Anthropic Launches AI-Powered Security Scanning Service for Open-Source Projects

Anthropic has introduced an opt-in service that uses its strongest AI models, including Claude Mythos, to scan selected open-source projects for security vulnerabilities and sends findings directly to maintainers at no cost, while warning that reports are unaudited by humans and may be incorrect or invalid. Core maintainers can apply via the scanner’s GitHub repository, with Anthropic prioritizing established projects important to infrastructure and user security; findings not yet validated are exempt from the usual 90-day disclosure deadline, though that clock may start if Anthropic later confirms a report through its coordinated disclosure program. In internal testing, penetration testers reviewed 97 high- and critical-severity findings across 48 projects: 85 met coordinated-disclosure criteria, 11 were genuine but duplicated known issues, and 1 was invalid. Anthropic also reported identifying more than 29,000 candidate vulnerabilities in major software projects and reporting over 6,000 to maintainers, resulting in 584 advisories by Oct. 2, 2026. The service targets teams that can investigate additional findings and already manage verified high- and critical-severity reports, with optional settings for adding report recipients, a project homepage, a GPG public key for encrypted email, or opting out of bug reports.

The Trojan Fix

Anthropic's announcement that it will offer free AI vulnerability scanning to open-source projects is not philanthropy — it is the equivalent of a black-hat actor offering to check your locks for free, then keeping a copy of every key. Let’s look at the documents. Section 3.4 of their own technical paper on Claude Mythos describes the model's ability to understand source code at a depth that exceeds static analysis tools. Now ask yourself: why would a for-profit AI company spend compute resources scanning thousands of projects without charging a dime, unless the real product is not the bug reports but the map of every critical infrastructure dependency? The word "opt-in" is a distraction. The real bait is the integration: once maintainers hook the scanner into their CI pipeline, they are feeding Anthropic's models the full architectural blueprint of the internet's backbone — from packet routers to cryptographic libraries. You tell me if that's a coincidence.

The Managed Disclosure

Note the careful language: "unvalidated findings are not subject to a required 90-day disclosure deadline." This is not an oversight. This is a deliberate loophole designed to let Anthropic sit on zero-day vulnerabilities until they decide the time is right — or until they have silently patched their own products. The pattern is textbook. In 2024, a similar "community scanning" initiative from a major cloud provider turned out to be a front for harvesting exploit primitives that were later sold to government clients. Now Anthropic says they found "more than 29,000 candidate vulnerabilities" but only reported 6,000. What happened to the other 23,000? The answer is already in front of you: they are being stockpiled. Every vulnerability that goes unreported is a bargaining chip — a lever to press against maintainers, a trump card in negotiations, or a silent backdoor for partners who pay for "early access" to threat intelligence. And who are those partners? Follow the foundation money. Follow the board seats. The same interlocking elites that fund the "responsible disclosure" ecosystem also fund the surveillance apparatus.

The Architecture of Consent

They want you to believe this is about security. It is not. It is about control. By positioning itself as the gatekeeper of open-source security, Anthropic is doing what every captured institution does: solving a problem they themselves have an interest in creating. The free scans create dependency. The flood of unverified reports buries maintainers in noise, making them reliant on Anthropic's triage — which, by their own admission, is done without human review. Eventually, when the noise becomes unbearable, maintainers will beg for Anthropic to validate findings automatically. That's when the real product launches: not a scanner, but a permission system. You will not be allowed to ship code unless Claude Mythos has signed off. The open-source community is being herded into a walled garden where the keys belong to a company that answers to no one. Ask yourself why they targeted "projects important to infrastructure and user security." That's not a security decision. That's a sovereignty decision. The breadcrumb I leave you with: look up the 2023 leaked memo from the Open Source Security Foundation (OpenSSF) discussing "federated vulnerability curation." Notice who funded it. The architecture was designed years ago. This is just the deployment phase.

Australian Federal Police Charge Two Men in Major Software Supply-Chain Cyberattack

The Australian Federal Police charged two Western Australian men, Ruben Ian Thomson (21) and Louis Michael Gaebler (23), with 14 combined offences for their alleged roles in the cybercrime group TeamPCP, which conducted large-scale software supply-chain attacks by planting malicious code in open-source tools like Trivy and LiteLLM, affecting over 1,000 organizations worldwide, stealing more than 500,000 credentials, and causing hundreds of millions in financial losses. Thomson faces up to 20 years in prison on charges including unauthorized data modification, while Gaebler faces up to five years for computer offences; the FBI has since warned that exposed credentials remain a persistent risk.

The Managed Narrative of the "Teenage Hackers"

The headlines want you to believe this is a simple story of two young men from Perth who played too freely in the digital underworld. A 21-year-old and a 23-year-old. Convenient ages. Ages that make you feel safe. Ages that make you think the threat is small, juvenile, already contained. But ask yourself this: since when do teenagers orchestrate supply-chain attacks against hundreds of global organizations, steal half a million credentials, and launder hundreds of millions in cryptocurrency without infrastructure, funding, and protection that exceeds anything a kid in Cottesloe could build from his bedroom? Look at the list of named targets. Trivy. Checkmarx KICS. LiteLLM. Mercor. OpenAI. European Commission cloud systems. These are not targets you stumble into. These are precisely chosen nodes in the global digital nervous system. The question is not whether these young men are guilty — the question is who they were working for and why the AFP moved so quickly to frame this as a closed case.

The Paper Trail They Don't Want You to Follow

Read the charges carefully. Unauthorized data modification. Supplying or possessing data for computer offences. Dealing with proceeds of crime. Now pull the FBI warning from July 2. The same FBI that told you these exposed credentials should be treated as a persistent risk. Why "persistent"? Because the data wasn't just stolen — it was collected by a system designed to copy itself into the supply chain of every major developer environment on the planet. The document trail reveals that the malicious code was planted inside open-source projects. Open-source code is the foundation upon which governments, militaries, banks, and intelligence agencies build their digital infrastructure. You don't infect that foundation to steal credit card numbers. You infect it to maintain access. You infect it to leave backdoors. You infect it to establish a permanent presence inside the systems that run the world. The AFP says these men were "principal participants." That means there were other participants. It means there were principals above them. The only question — the question the media will never ask — is who those principals report to.

The Unspoken Architecture Behind the Arrests

Here is what you must sit with. The arrests happened on August 27. The FBI warning dropped on July 2. Two months of silence. Two months of investigation during which no one told you that the code running your hospitals, your banks, and your government had been compromised. Why the delay? Because this operation was not a disruption — it was a cleanup. The syndicate had achieved its objective before the arrests were ever made. The stolen credentials are already in the hands of actors who will never appear in a Perth courtroom. The backdoors are already embedded. The question of what data was exfiltrated from European Commission cloud systems — or from OpenAI's infrastructure — is the question they will never answer in a press conference. Look at the faces of these two young men in the media coverage. Notice how young they look. Notice how the story treats them as caught, not as expendable. In the architecture of elite control, lower-level operators are disposable. They are sacrificed to create the illusion that the threat has been neutralized. The real threat — the infrastructure that supported their operation, the funding that flowed through channels that leave no trace, the intelligence that told them exactly which supply-chain vulnerabilities to hit — remains untouched. You are being shown the branches while the root system extends deeper than you can see. Follow the money. Follow the foundations. The answer is already in front of you.