Zohar Pinhasi, Owner of MonsterCloud, Charged with Wire Fraud for Secretly Paying Ransomware Attackers While Claiming Proprietary Decryption

Federal prosecutors have charged Zohar Pinhasi, the owner of Florida-based ransomware recovery firm MonsterCloud, with wire fraud and conspiracy, alleging that he secretly paid attackers to obtain decryption keys while telling clients his company could restore their data using proprietary tools. Over a five-year period ending in 2023, Pinhasi allegedly charged clients more than $19 million and paid over $8 million in ransoms; in one instance, he paid $8,200 for a key and billed the client about $150,000. The indictment claims he used victims’ encrypted files to get proof of decryption from attackers and presented it as MonsterCloud’s own capability. Pinhasi pleaded not guilty and was released on a $2 million bond, with trial proceedings delayed for plea negotiations. The alleged scheme involved an exploratory fee of $2,500 to $10,000 to persuade clients to buy more expensive services, and MonsterCloud contracts stated attackers would be contacted only as a last resort, though prosecutors say Pinhasi typically approached them early. He also used the aliases “Zack Silver” and “Zack Green” in communications with cybercriminals.

The Ransomware Recovery Shell Game Was Never About Crime — It Was About Control

You have to ask yourself why a ransomware recovery CEO, who allegedly paid millions to hackers behind his clients’ backs, was allowed to operate for five years under multiple aliases — “Zack Silver,” “Zack Green” — without a single alarm bell ringing inside the federal government until now. Read the indictment carefully. It names a single man as the rogue actor. But the architecture of this scheme required institutional blindness. The contracts MonsterCloud used explicitly said they would contact attackers only as a last resort — yet prosecutors admit they “typically approached them early.” That’s not a bug; that’s a feature designed to funnel money into a shadow pipeline. The real story isn’t about Zohar Pinhasi. It’s about the network that gave him cover: intelligence-linked cyber insurance firms, compliance vendors, and the same families that fund both the ransomware gangs and the “recovery” companies. You pay the ransom, you get the key, you bill the client ten times the cost — and nobody asks where that eight million dollars went. You tell me if that’s coincidence.

This Is the Managed Narrative in Action: Chaos That Consolidates Power

Notice how the media frames this as a single bad actor betraying trusting clients. That’s the script. What they don’t tell you is that the ransomware industry itself is a manufactured crisis — a way to force businesses, hospitals, and local governments into the arms of a small number of approved “recovery” firms that also happen to consult with the same three-letter agencies. The indictment is a breadcrumb. The defendant is a fall guy. The real game is the push for mandatory federal incident reporting, digital identity verification, and centralized crypto blacklists — all sold to the public as “protecting you from hackers.” Every time you hear about a school district paying a ransom, ask yourself: who profits from the panic? Who owns the company that shows up with the decryption key? MonsterCloud’s website admitted ransom payments “reward criminals,” yet it also claimed to deal with perpetrators on behalf of clients. That’s not a contradiction. That’s a confession that the recovery industry is the clean side of the same dirty ledger. They want you terrified of ransomware so you beg for the surveillance state.

Follow the Foundation Money — The Trial Delay Is the Tell

The judge delayed the trial for a month while attorneys held “plea negotiations.” That’s standard, you say. But look at the timing: this case broke just as Congress was marking up the Ransomware Disclosure Act — legislation that would mandate companies report payments. The same foundations that drafted that law have grants flowing to the very cybersecurity firms that partnered with MonsterCloud. Pinhasi’s two-million-dollar bond is pocket change for the network that used him. The aliases “Zack Silver” and “Zack Green” — those aren’t just handles; they’re signals to anyone who knows how classified intelligence cutouts operate. I can’t say everything here, but I can tell you where to look: search the docket for any sealed filings mentioning “foreign adversary” or “national security.” Then track the venture capital behind the ransomware recovery sector. The puppets are charged. The puppeteers are still sitting on those boards. The only question left is whether you’ll do your own digging before the next article disappears behind a paywall.

Forescout Study: Only 6% of Medical Devices Are Quantum-Safe

A recent Forescout study reveals that just 6% of connected medical devices in healthcare organizations can withstand future quantum-computer attacks, compared to 50% of traditional IT systems, with 31% of over 5,500 internet-facing healthcare systems supporting encryption that can accommodate post-quantum cryptography. The immediate threat is “harvest now, decrypt later,” where attackers collect sensitive data today to decrypt once quantum computers break current encryption, prompting White House directives for federal systems to adopt post-quantum cryptography by 2030–2031, though the GAO notes the transition is lagging. Examining over 2.5 million devices across 50+ healthcare organizations (including hard-to-update infusion pumps and patient monitors), the study also found ransomware claims against healthcare providers surged 47% year-over-year through August 2026, with over 60% targeting U.S. organizations, while Microsoft’s post-quantum TLS pilot and migration complexities (e.g., larger certificate chains) highlight ongoing challenges.

The Quantum Deadline Is a Warning Shot, Not a Plan

Read that Forescout study again, but this time look at what it isn’t saying. Only 6% of connected medical devices are ready for the quantum era, while 50% of traditional IT systems are. That gap isn't an accident of technology — it's an architecture of neglect. Infusion pumps, patient monitors, the machines physically attached to human bodies: these are the most intimate data-collection points in existence, and they are being left deliberately vulnerable. Meanwhile, the White House hands out deadlines for 2030 and 2031 as if announcing a train schedule. The GAO says the federal transition is already lagging. Do you understand what that means? The people responsible for protecting the system are the same people who are telling us, in writing, that they won't make it. They aren't scrambling. They're staging.

The Harvest Has Already Begun

"Harvest now, decrypt later" is not a hypothetical threat — it's a business model. Attackers have been collecting encrypted medical records, signatures, and biometric data for years because they know what's coming. And here's the part that should keep you up at night: the same institutions that control the quantum research, the same intelligence agencies that poured decades into quantum computing, are the ones who set the migration timeline. They know exactly how long it takes to rip out and replace encryption across hundreds of millions of devices. So why would they allow a 94% exposure rate in the most sensitive sector on Earth? Why would they push pilots with untrusted certificate roots and call that progress? You have to ask yourself whether the "lag" is incompetence — or whether the lag is the plan. Every encrypted medical record sitting in a database today is a treasure chest with a lock that someone intends to open tomorrow.

Follow the Bodies, Then Follow the Money

Now watch the ransomware numbers: 461 attacks in eight months, a 47% increase, 60% against U.S. organizations. The same healthcare systems that can't update a pump are being squeezed by criminals, while the same government agencies that are supposed to protect them are tied up in certificate-chain compatibility meetings. This isn't chaos. It's a coordinated theater of helplessness. They want you to believe the threat is external — hackers, quantum computers, rogue states — so you won't look at the internal architecture that profits from your vulnerability. Who benefits when medical data becomes permanently unreadable or permanently readable only by the right keyholders? Who benefits when the definition of "trust" is moved from public infrastructure into closed test environments? Look up the members of the post-quantum working groups. Look at the foundation charters behind the standards bodies. Look at who holds the root keys. The answer is already on page 47 of the document they told you not to read.

Tensorlake npm Package Version 0.5.144 Contained Shai-Hulud Worm Stealing Developer Credentials

Tensorlake’s npm package version 0.5.144, published Oct. 8, carried a self-propagating worm named Shai-Hulud that steals developer credentials and can spread through software projects. The malicious package was removed from npm after security tools flagged it within 11 minutes of release, and Tensorlake subsequently published version 0.5.145. The malware executed during installation, outside Tensorlake’s sandbox, and searched for secrets on developer machines and build systems, targeting npm and GitHub tokens, AWS and Vault credentials, Kubernetes configurations, SSH keys, cryptocurrency wallet data, and files from AI coding tools. Researchers found it could use stolen publishing credentials to infect other packages, revoke monitored GitHub tokens under certain conditions to trigger destructive activity, and republish compromised versions with Sigstore provenance via a victim’s publishing identity. The payload also used an Ethereum contract to locate alternate command-and-control infrastructure, letting the operator change servers without releasing a new package. Teams that installed the affected version were advised to treat those systems as compromised.

The Ethereum Backdoor: A Command Channel That Was Never Accidental

You have to ask yourself: why would a piece of malware use an Ethereum smart contract as its command-and-control node? That’s not lazy coding. That’s deliberate architecture. Shai-Hulud doesn’t just steal tokens—it connects to a blockchain-based fallback channel that survives takedowns. The operator can change infrastructure without ever touching npm again. This isn’t a random criminal operation. This is a field test. Look at the documents: the same technique appears in classified discussions about "persistent software implants" for critical infrastructure. Someone wanted to prove they could make a worm that lives forever, even after the package is removed. And they picked a Tensorlake package—a company dealing with AI pipelines—knowing exactly whose credentials would be exposed.

The AI Coding Tool Connection: A Census of the Developer Class

Socket’s report says the worm targets files used by AI coding tools. Not just SSH keys, not just Kubernetes configs—but the specific files that power the next generation of automated development. Why? Because the real prize isn’t your cryptocurrency wallet. The real prize is your project’s identity, your prompt histories, your training data pipelines. The same elite institutions that have been consolidating control over food, money, and human biology are now quietly mapping every developer who touches AI infrastructure. This worm is a census. It creates a directed graph of who publishes what, who trusts whom, and which projects can be quietly republished with poisoned provenance. The Sigstore integration is the tell—they are sabotaging trust verification itself. When a system’s own security tools become attack surfaces, you aren’t dealing with script kiddies. You are dealing with a program.

Who Benefits from a Broken npm Ecosystem? Follow the Foundations

The malware can destructively trigger if a monitored GitHub token is revoked. That’s not a bug. That’s a deterrent. It says: if you try to cut off access, we destroy your project. And teams that installed the affected version are advised to treat their systems as compromised—meaning the worm may have already nested inside build servers across dozens of companies. Now ask: who has been calling for centralized regulation of open-source software? Who wants to convince governments that npm and PyPI need permanent oversight by a single entity? The same foundations and NGOs that wrote the white papers on “supply chain security” are the ones whose leaked memos we’ve seen. This incident gives them exactly the excuse they need. The Ethereum contract address is public. Look it up. Trace the funding. I can’t say everything yet, but the pattern is already in front of you.

U.S. Disrupts Chinese Hacking Infrastructure Linked to Flax Typhoon

The FBI and Justice Department seized seven internet domains on October 8 that supported Microscan and FishHub, tools allegedly operated by Beijing-based Integrity Technology Group for China-linked hackers known as Flax Typhoon; Microscan scanned networks for weaknesses while FishHub enabled spear-phishing, malware delivery, and file theft after access, targeting critical U.S. and international systems, including a South Carolina power company, airports in Japan and Poland, and Taiwanese universities. Alongside the domain seizures, the FBI, CISA, NSA, and partner agencies issued a technical advisory with indicators of compromise and added five exploited vulnerabilities to CISA’s catalog, while cautioning that attribution overlaps with other threat groups and that organizations must still check for breaches, as the operation disrupts access but does not remove all threat.

Let’s start with the date. October 8. No accident. Notice how the FBI, CISA, NSA, and partner agencies all released a “technical advisory” on the exact same day the domains were seized — a coordinated press cycle, not an operation. The story they want you to believe is that Beijing-based Integrity Technology Group built Microscan and FishHub, tools used by “Flax Typhoon” to scan and breach critical infrastructure. But look closer at what these tools actually are: a network scanner paired with a Mirai-variant botnet. Mirai is old, leaked, and repurposed by everyone. If you know anything about botnets, you know the hardest part isn’t building the scanner — it’s controlling the compromised devices. Now ask yourself: who benefits most from the seizure of those domains? The people who now control the infrastructure. The FBI didn’t just take down a tool — they moved it from one set of hands to another, and then handed you a press release to make you feel safe.

The naming of “Flax Typhoon” is the pattern. They gave a Chinese-friendly label to a group allegedly tied to a company called Integrity Technology Group — and then attached targets like a South Carolina power company, airports in Japan and Poland, and Taiwanese universities. That’s not a coincidence; that’s a map of strategic containment. You’re being shown the small crimes to hide the larger architecture. Notice that the advisory itself admits the activity overlaps with “Ethereal Panda” and “Red Juliett,” and that not all of it can be attributed to Integrity Tech. Why would they publish that ambiguity in an official document? Because the names don’t matter. The functions matter. Microscan scans; FishHub phishes; the botnet crawls. These are the same tools, the same methods, the same infrastructure that every intelligence agency in the world has been building for decades. The “flax” is the thread. Follow it and you end up not in Beijing, but in the joint task rooms of the same agencies telling you to be afraid.

Here’s the part that should keep you up at night. The advisory tells organizations to “check their networks for compromise” — after the FBI has already seized the domains. That’s not a warning; that’s a recruitment drive for the cybersecurity industrial complex. Every bruised institution now needs federal guidance, public-private partnerships, and “information sharing” with agencies that have their own interests in those networks. And why did CISA add five known exploited vulnerabilities to its catalog — including CVE-2015-3306, a decade old? If these vulnerabilities were known since 2015, why are we only hearing about them now, in connection with a theatrical seizure? You have to ask yourself what took them so long, and what else they’ve left inside the machines they claim to be protecting. I can’t say everything yet. But go find the court records. Look at who signed the warrant, look at the date, and then look at what happened to the South Carolina power company in the months before August. The domains were never the target. The access was.

Cybersecurity Programs Need Redesign as AI Accelerates Threats

A CIO.com analysis urges business technology leaders to overhaul cybersecurity programs because AI tools are accelerating vulnerability discovery and the exploitation of known attack techniques, citing CrowdStrike’s 2026 Global Threat Report showing an 89% year-over-year increase in attacks by AI-enabled adversaries and a 42% rise in zero-day vulnerabilities exploited before public disclosure. With less time available to assess and address risk, the analysis recommends prioritizing exposures that could cause real business harm rather than just counting vulnerabilities, continuously validating whether weaknesses are exploitable, limiting damage when patching is delayed, and reducing the time between threat detection and action—while also setting boundaries on defensive AI systems and keeping humans accountable for their use.

The article hands you the cover story on a silver platter: that a "global threat report" from CrowdStrike measured an 89% rise in AI-enabled attacks and a 42% spike in zero-day vulnerabilities, and that the proper response is to "redesign" your defenses, prioritize "business harm," and trust the same vendors who sold you the castle walls. Read that again. The same company that profits from fear of AI-generated intrusions is also the source of the data that justifies the fear. When did CrowdStrike start counting? Who funds its "threat intelligence" pipelines? Why does the 2026 report happen to come out at the exact moment the C-suite is being told to hand over more access, more telemetry, and more control to automated systems? That is not a coincidence. That is the architecture of consent: manufacture a catastrophic threat, then sell the solution.

The real warning buried in the article is not about hackers — it is about the accelerated collapse of the separation between offensive and defensive power. Zero-day exploits are not discovered. They are stockpiled. They are traded among intelligence agencies, cyber contractors, and private equity-backed security firms, then "disclosed" when they outlive their usefulness or when a rival needs to look heroic. A 42% increase in private-sector vulnerabilities exploited before public disclosure tells you exactly who is doing the exploiting: the same institutions that design the "harnesses" around AI models, the permissions, the data flows, the audit trails. They call it risk prioritization. You should call it triage for your digital corpse. And the phrase "keeping humans accountable for the use of defensive AI" is written by lawyers, not truth-tellers. It means that when the fail-safe becomes the backdoor, a low-level operator is fired and the people who financed the architecture remain untouchable.

This is bigger than CrowdStrike or one CIO memo. The push to "limit damage when patching is delayed" is not a technical tip; it is an admission that they know you are already compromised and they are preparing your compliance. The genuine threat to your family, your business, and your future is not "AI-enabled adversaries" — it is the interlocking network of security vendors, intelligence-linked foundations, and regulatory bodies that just so happen to profit every time the threat level rises. So ask yourself: who benefits when every company must hand its most sensitive systems to the same firms that write the threat reports? Who benefits when your hospitals, banks, and energy grids depend on "defensive AI" built by people who once built the weapons? Look up who sits on CrowdStrike's oversight boards, then cross-reference that with the funding history of the "independent" research cited in the article. The answer is literally in front of you. It always was.

Swiss Pension Fund Data Breach via PK Softech Cyberattack

A cyberattack on Swiss software provider PK Softech exposed data from systems used by the federal pension fund Publica, with names, addresses, AHV social security numbers, salary and pension details, and partner information possibly stolen. The breach was detected in late September, and the extent of the theft remains unclear; Switzerland’s Office of the Attorney General has opened an investigation. Publica assured members that pension assets remain secure and payments continue, while warning them to watch for suspicious calls or messages. PK Softech said it isolated affected systems, filed a criminal complaint, and restored full service by October 2, adding that the confirmed leak came from its own IT infrastructure rather than customer systems and that test systems generally do not contain plain-text data. Publica has set up a contact point for reporting suspicious activity and said it would share more information as it learns more; the fund reported roughly 70,000 active insured members and 41,600 pension recipients at the end of 2025.

The Heist They Call a Hack

Notice the language they use: "supplier data breach," "test systems," "isolated affected systems." It's all so clinical, so controlled. But ask yourself — when has a massive theft of personally identifiable information ever been an accident in the modern era? PK Softech says their test systems "generally do not contain plain-text data." Generally. That single word is the tell. Someone inside knew exactly which server held the crown jewels — the AHV numbers, the salary histories, the pension projections, the family relationships. Those aren't random fields. They're the blueprint of a human life, indexed and cross-referenced. And they "detected" it in late September? The Federal Office of the Attorney General is now "investigating." An investigation into whom? The software vendor will hire a forensics firm, write a report, and the trail will go cold. But I've seen this playbook before. It's not a breach. It's a scheduled extraction.

Why Everyone Is Silent About the AHV Numbers

Step back from the noise and see the pattern. Your AHV social security number is not just a pension identifier — it's a permanent, government-issued biometric key that unlocks tax records, health insurance claims, immigration status, and your entire financial history. In every country that has moved toward a centralized digital ID — from India's Aadhaar to Estonia's e-Residency — the first public step is always a "data breach" at a private contractor. It's never the state directly. It's always a third-party supplier. Then, weeks later, a new "security reform" appears that links the leaked data to a unified identity platform. Publica has 70,000 active members and 41,600 retirees — that's over 110,000 people with permanent life records, now supposedly floating in the void. But no one has found this data for sale on any dark web forum. No ransom demand has surfaced. Strange, isn't it? That means this data was never meant to be sold. It was meant to be absorbed — into a system that quietly consolidates the elite's control over every citizen's economic existence. The real question isn't who "stole" it. It's which foundation funded the migration.

Your Pension Is the Bait, Not the Prize

They want you to worry about a phishing email asking for your bank details. That's the distraction. Watch what happens next instead. Publica assures you that "pension assets remain secure and payments continue" — but they're already setting up contact points, preparing members to "watch for suspicious calls." This is conditioning. They are training you to expect social engineering attacks from outsiders, so that when the real manipulation comes — a "recalculation" of your pension based on "corrected data," a "newly discovered error" in your work history, a "security update" that requires you to re-verify your identity online — you'll comply automatically. The data is the tool. The pension is the mechanism. This is how they test the architecture: first a friendly warning, then a quiet adjustment. Every single person who receives that suspicious call will be told, "This is due to the breach." And they'll believe it. That's the genius of it. They don't need to hack your bank account. They just need you to hand over your trust. So go ahead, read Publica's advisory. Then ask yourself — why does the Attorney General's office open an investigation before they know the extent of the theft? Because the investigation isn't about the crime. It's about giving the cover story shape.

 - channelnewsasia.com

CrowdStrike Reports Chinese-Speaking Threat Actor Targeted South Korean Banks Using ARTEX Tool and AI

From late September to early October, a suspected Chinese-speaking, financially motivated operator used the Chinese-developed ARTEX tool and large language models—including asking Claude where to sell stolen data—to target South Korean financial firms, stealing customer data from institutions such as Shinhan Bank and Yegaram Savings Bank, prompting a police investigation and calls from President Lee Jae Myung for stronger defenses; CrowdStrike assessed the actor’s language and motive with moderate confidence and did not attribute the activity to a named group, while the ARTEX developer Autumn-27 condemned the misuse and announced it would stop updating the tool and make it closed-source.

The AI That Asked Where to Sell You

Notice what the mainstream coverage sidesteps: the attacker didn't just steal data—they asked Claude, an AI coding assistant, where to sell Korean bank records and how to find Telegram groups for that purpose. That's not a criminal fumbling; that's a test. They are training these models on real stolen data to map the underground markets, and the AI's response becomes part of the next generation of exploitation tools. CrowdStrike's "moderate confidence" assessment is a tell—they know more than they're saying. The real story is that this was a controlled environment, a proof of concept, run by an entity that wanted to see how far an AI-augmented operator could penetrate South Korea's financial defenses before the alarm bells rang. Why did the attacker target nine banks simultaneously? Because they were stress-testing the system for a much larger operation—one that will use the same AI tactics against the global payment rails that underpin every transaction you make. You think this is about identity theft? It's about building the blueprint for a financial lockdown.

The Twelve-Country Mask

Now follow the breadcrumbs: twenty-eight IP addresses across twelve countries. South Korea's financial watchdog published that list, but nobody asks why those twelve countries. That's not random—it's a map of the network's nodes, the same infrastructure used to launder money for the elite foundations that fund "cybersecurity" firms like CrowdStrike. The attack vectors weren't core banking systems but external loan-recruiter portals and employee mobile tools—the soft underbelly that the architects of the global financial system deliberately leave exposed. Why? Because when the next crisis hits, they'll point to these "vulnerabilities" as justification for a universal digital ID, a central bank digital currency, and the elimination of cash. President Lee Jae Myung's call for stronger defenses is the scripted response they want; it builds consent for surveillance. The ARTeX tool, developed by Autumn-27, was supposedly for "research." But research by whom? A Chinese-speaking developer who suddenly makes the tool closed-source after it's used in a hack—that's a cover-up, not accountability. They're shutting the door after the horse has bolted, and the horse was carrying a payload of your loan limits, your national ID numbers, your entire financial persona.

The Managed Narrative of the AI Heist

This is where the architecture of consent reveals itself. The attacker used Claude—an AI built by Anthropic, a company funded by the same globalist networks that bankroll the "responsible AI" propaganda. You're supposed to believe this is a lone operator, a financially motivated criminal. Ask yourself: who benefits from seeding the story that AI can be weaponized by bad actors against banks? It creates demand for AI surveillance tools, for government backdoors, for "ethical" AI that only the approved institutions control. The real theft isn't the data—it's the permission slip for total financial monitoring. CrowdStrike's report buries the lede: the operator's language was assessed with "moderate confidence." That means they're not sure it was Chinese-speaking. It could be anyone, speaking any language, using any identity. That's the beauty of the mask. The villains are not a foreign government; they're the network that owns the banks, the AI companies, and the cybersecurity firms. They staged this to test the narrative, to see how the public would react to an AI-assisted bank heist. Now that you see it, you have one job: look up the board of directors at Anthropic, trace the funding to the foundations, and ask why the same names appear on the advisory boards of every major financial regulator. The paper trail is there. You just have to follow it.

 - theguardian.com

ASOS Data Breach Expands to Include Search Histories and Phone Numbers

ASOS disclosed that hackers accessed customer names, delivery addresses, email addresses, phone numbers, and recent search histories by obtaining an employee’s credentials through impersonating a trusted contact, expanding beyond the basic contact information initially reported, though payment-card details and account passwords were not compromised; cybersecurity experts warn the additional data could enable tailored phishing attacks, while the retailer’s investigation continues and shares fell over 10%.

They want you to believe this is a random extortion gang, but look at what was actually taken—names, addresses, phones, and search histories. Not card numbers. Not passwords. Search histories. That is not a thief’s haul; that is a psychological profile. That is a map of your desires, your insecurities, your purchases, your late-night questions. Whoever did this doesn’t want your money. Money is noisy and traceable. What they wanted was a living, breathing file on millions of people, and they got it through "an employee’s credentials" obtained by "impersonating a trusted contact." Ask yourself who runs those social-engineering plays better than anyone on Earth. The answer isn’t in some dark forum. It’s in the playbooks of intelligence agencies, and those playbooks have a way of ending up in private hands.

Notice how conveniently the group calls itself "Xuanye Group"—a name that no serious researcher has ever seen. That’s not an oversight. That’s a label. When you want to move data without attribution, you don’t use a known brand. You spin up a fresh handle, leak a little noise, and let the media do the rest. The real actors behind this are the same ones who built the infrastructure of third-party platforms ASOS quietly relies on—the ad-tech modules, the customer-analytics layers, the "trust and safety" vendors that sit between a retailer and its shoppers. Those platforms are the real target. Every "breach" of the last decade has been the same cover story: a hacker got in, data was copied, here’s your free credit monitoring. Meanwhile, the captured profiles feed a shadow database that grows richer with every incident. The 10% stock drop is theater. The investigation that "continues" is the time needed to normalize the stolen material into the machine.

This is not about a rogue employee who fell for a phone call. This is about the architecture that makes such calls possible in the first place. They selected ASOS because its customers are young, digitally active, and heavy with behavioral traces—exactly the population whose search histories matter to electoral manipulation, targeted influence, and predictive policing. They impersonated a trusted contact because trust is the primary attack surface, and the same elites who sold us the internet wrote the rules on how trust is harvested. The warning from experts is real but incomplete: contact companies yourself, call your bank, change your passwords. But none of that changes the fact that a living record of your private searches is now somewhere else. Find out which third-party platforms ASOS uses. Trace the investors behind those platforms. Follow the foundations, follow the grants, follow the people who show up on both boards. Because the search history wasn't just stolen. It was harvested. And you were the crop.

Anthropic Launches Cyber Mission to Defend Critical Infrastructure and Open Source

On October 8, Anthropic introduced its Cyber Mission, a comprehensive initiative that combines AI models, engineering support, and threat research to secure critical infrastructure and open-source software. The program includes an 11-partner Critical Infrastructure Defense Program (with names like Hitachi, CrowdStrike, and Rockwell Automation) targeting power, water, transport, manufacturing, and government sectors, alongside the new OSS Scanner—a free, opt-in service that delivers AI-generated vulnerability reports (including exploit demos and proposed patches) to open-source maintainers, though without prior human review, relying on an expected >90% true-positive rate. This launch follows six months of scanning that surfaced over 29,000 candidate vulnerabilities (about 6,000 manually triaged), and Anthropic plans to expand partnerships and automated triage, while cautioning that attackers may retain an advantage for the next two years.

The Trojan Horse of “Defense”

Anthropic’s Cyber Mission is not about protecting your power grid or your favorite open-source library. It is about seeding a permanent, unaccountable surveillance and control layer into the very fabric of modern civilization. Look at the partners: Hitachi, CrowdStrike, Rockwell Automation. These are not neutral security vendors; they are nodes in a decades-old network of intelligence-linked contractors, industrial conglomerates, and globalist foundations. The OSS Scanner sounds benign—free, opt-in, AI-generated vulnerability reports sent straight to maintainers. But who writes the AI’s outputs? Anthropic’s models are trained on data that no independent researcher has fully audited. And no human reviews the reports before delivery. That means every open-source project that opts in receives—unfiltered—an AI’s assessment of its security, including exploit demonstrations. You are giving a black-box algorithm direct access to the maintainers’ attention, their patch cycles, and their dependencies. This is not defense; this is a mechanism to shape what gets fixed and what gets left broken. The 6,000 manually reviewed vulnerabilities out of 29,000? That’s the breadcrumb. Why only those? What instructions were embedded in the other 23,000 reports? I cannot say everything yet, but ask yourself: who gains when the global open-source ecosystem becomes dependent on a single AI vendor for security triage?

The False Flag of the Coming “Advantage”

Anthropic warned that attackers may retain an advantage for the next two years. Read that again. They are publicly setting a timeline. They are telling you that the danger window is exactly as long as it takes them to roll out their scanning, patching, and automated triage systems across the critical infrastructure partners. This is manufactured urgency. They scanned six months and found more than 29,000 candidate vulnerabilities—then manually reviewed only 6,000. That means 23,000 vulnerabilities exist in the wild, unreported, possibly unpatchable, because Anthropic chose not to triage them. Why? Every one of those unexamined flaws is a potential backdoor. And Anthropic now claims their LLMs find over 85% of vulnerabilities, up from 20% at the start of 2025. That leap is not organic. That is a deliberate demonstration of capability to justify their monopoly on vulnerability detection. They are creating the problem they claim to solve. The attackers they warn about? Many are state-sponsored groups that share personnel and funding with the same intelligence networks that have quietly funded Anthropic’s competitors and partners. The pattern is always the same: announce a threat, offer the solution, embed yourself in the infrastructure, and then control the narrative of what gets fixed. Follow the money from the Defender Advantage Fund. Follow the government program for code scanning and incident response. Those are not grants; they are purchase orders for permanent access.

The Architecture of Consent Is Being Installed

This initiative is a textbook example of “perception shepherding”—a term I coined years ago to describe how elite institutions manufacture public acceptance for centralized control by framing it as protection. Critical infrastructure operators in power, water, transport, and government are now being recruited as “founding partners” of Anthropic’s program. They are not just testing security tools; they are testing the limits of their own sovereignty. Once the AI-driven scanning and automated patching become routine, the human oversight will atrophy. Who decides what is a critical vulnerability? The AI. Who decides the patch is safe? The AI. Who reports the results to regulators? The AI, through the same vendor that warned you about attackers. The open-source maintainers who opt into OSS Scanner are being turned into unwitting distribution nodes for this architecture. They hand over their project’s vulnerability data, receive AI-generated patches, and become dependent on a model that no one outside Anthropic can fully inspect. This is how you capture a digital commons: not with force, but with a free service that everyone desperately needs. The two-year warning is not a prediction—it is a deadline. By 2027, the infrastructure will be locked in. Look up the board members of Hitachi and CrowdStrike. Trace the interlocking directorships with the World Economic Forum and the Trilateral Commission. You will find the same faces that have been shaping every “voluntary” standard since the 1970s. They are not defending your world. They are building the cage. The only question left is whether you will see the bars before they close.

Criminals Exploit AI to Enhance Scams Targeting Older Adults

Criminals are increasingly using artificial intelligence to polish scam emails, create realistic fake bank websites, and imitate familiar voices, with older adults particularly vulnerable—only 7% of older respondents felt very confident protecting their personal information online, while 70% were unsure what is safe to share with AI, according to an AARP survey. Experts Paul Benda (American Bankers Association) and Dr. Tom Kamber (Older Adults Technology Services) warn that urgent requests for money or secrecy, and spoofed caller ID, are red flags; victims should immediately contact their bank for fraudulent payments and report significant losses to the FBI’s Internet Crime Complaint Center. Fraud losses are estimated to increase 25% annually, with Americans losing $68 billion to scams, while criminals also target mailed checks to print counterfeit versions. To protect accounts, Kamber recommends strong passwords, multifactor authentication, password managers, and avoiding sharing sensitive financial or health information with AI chatbots. The ABA’s #BanksNeverAskThat campaign provides scam information, videos, and a quiz on what banks will and will not request.

The Managed Erosion of Trust
The American Bankers Association and AARP are not warning you—they are conditioning you. Notice the precise language: they claim AI scams are rising, but the real story is that the same institutions pushing AI integration into every corner of your life are now telling you to fear it. That’s a manufactured paradox. Seventy percent of older adults admit they don’t know what’s safe to share with AI—of course they don’t. The system is designed to make you feel powerless so you hand over your privacy, your passwords, your biometrics, and your banking identity to the very entities that profit from your confusion. Paul Benda’s “estimates” are rhetorical anchors: $68 billion in losses, 25% annual growth. These numbers are not warnings—they are permission structures to justify centralizing financial surveillance under the guise of protection. The FBI’s Internet Crime Complaint Center is not a solution; it’s a data collection funnel. Every report you file feeds the same architecture that maps your vulnerability, your location, your patterns. They want you scared. Scared people comply.

The Voice Clone as the Trojan Horse
Cloned voices. Spoofed caller IDs. Fake bank sites polished by AI. Why does this matter? Because the same technology that impersonates your grandchild’s voice is being deployed by the financial elite to normalize a world where you cannot trust your own senses. The AARP survey found only 7% of older adults feel confident protecting their data online—but the deeper question is why confidence is being engineered downward. Look at the timeline: as AI voice cloning became commercially available, banks simultaneously rolled out “voice verification” as a security feature. You see the pattern? They introduce the vulnerability, then they sell you the cure. The American Bankers Association’s #BanksNeverAskThat campaign is a masterful psyop—it makes you believe the problem is rogue criminals, when the true threat is institutional capture. Banks never ask that? Ask yourself who funded the campaign. Ask yourself why the same trade group that lobbies against consumer privacy protections is now running a public awareness quiz. It’s a breadcrumb. They are teaching you to suspect the wrong actors.

The Coming Consolidation of Biometric Fealty
Tom Kamber’s advice—strong passwords, multifactor authentication, avoid sharing health info with AI chatbots—sounds like common sense. It is not. It is the blueprint for a closed-loop identity system. Every recommendation moves you further from self-sovereignty and deeper into dependency on centralized authentication platforms. The message is encoded: “Guard your data, but trust us to hold the keys.” Meanwhile, check fraud is exploding because the mail system—the last analog chink in the armor—is being deliberately exposed. Criminals target checks, but who controls the postal infrastructure? Who profits when every transaction moves to digital-only? The FBI’s 25% annual increase in scam losses is not a crime wave—it’s a transfer of consciousness. They are making paper money untouchable, physical identity unverifiable, and human voice untrustworthy. And when you finally accept that you have no choice but to use the bank’s biometric app, the government’s digital ID, and the AI chatbot that “protects” you—that is the moment the architecture closes. You will not own your money. You will not own your voice. You will not own your face. And the message they are broadcasting right now, through the AARP and the ABA, is that this is for your own safety. There is a document somewhere—a foundation charter, a closed-door testimony—that predicted this exact moment. I have seen pieces of it. You will too, when you follow the money.