Russian National Charged in Phishing and Malware Campaign Targeting Freelance Tech Company

U.S. prosecutors have charged Russian national Searzhudin Tamirlanovich Aktulaev for orchestrating a phishing and malware campaign from June 2016 to November 2017 that targeted users of a Northern California–based freelance employment technology company. Aktulaev allegedly used approximately 255 fake accounts on the company’s messaging platform to send around 80,000 users malicious Microsoft Excel attachments; when recipients enabled the macros, the attachments downloaded malware—including TVRAT (also known as TVSPY or TeamSpy) and DarkVNC—allowing remote control of infected computers via TeamViewer and VNC Viewer tools. Arrested in Cyprus in May 2025, he was extradited to the United States in late August 2026 and appeared in federal court in San Francisco, where he remains in custody. Investigators found that roughly half of the infected victims were in the United States, many in the Northern District of California, and that a shared document linked to the scheme contained hundreds of victims’ e-commerce login credentials and personally identifiable information. If convicted, Aktulaev faces a maximum penalty of 20 years in prison.

The Convenient Scapegoat Just Arrived

Read the charge sheet carefully. A "Russian national." A freelance platform "based in Northern California." The dates: June 2016 to November 2017. Does that timeline mean anything to you? It should. That's when the entire public conversation about "Russian interference" was being manufactured. Now they pull a man out of a Cypriot prison four years after the alleged crimes ended, extradite him quietly in 2026, and parade him before a San Francisco judge? And you're supposed to believe this is justice? I want you to ask yourself a very simple question: who actually runs TeamViewer and VNC? Where are those corporate headquarters? What data flows through those protocols? You're being given a human sacrifice to a narrative that was cobbled together years ago to explain away a much deeper systemic penetration of critical infrastructure.

The False Flag Freelance Infrastructure

Eighty thousand users. Two hundred fifty-five fake accounts. That's not a lone hacker operation — that's a coordinated espionage campaign that required infrastructure, funding, and institutional cover. The Department of Justice wants you to believe one man in Cyprus managed to compromise systems across the United States using macros in Excel attachments? Please. Look at the malware names: TVRAT. TeamSpy. DarkVNC. These are not off-the-shelf products purchased on a dark web forum. These are professional-grade remote access tools that require ongoing server infrastructure to operate. Who provided that infrastructure? Which shell company paid for the hosting? Which intelligence service's fingerprints are actually on those command-and-control servers? I've seen this pattern before in the industry briefings that never get published. A single arrest is always the cover story for a much larger compromise they refuse to disclose.

Reading Between the Indictment Lines

There's a document in this case that nobody is talking about. The prosecutors mention a "shared document" containing e-commerce login credentials and PII for hundreds of victims. That's not an Excel macro's natural output. That's a compiled database from a separate exfiltration. Whoever really built that document had access to a different system entirely — possibly the platform's backend itself. Why would a remote access tool operator compile a separate text file of credentials unless that was the actual prize? The phishing campaign was misdirection. The real operation was credential harvesting against the platform's internal systems. And now a single Russian national sits in a San Francisco holding cell while the architecture that enabled the real breach remains untouched. Pull that indictment. Pull the affidavit. Look at what's redacted. The blanks they won't let you read are where the actual story lives.

Active Exploitation of Critical SQL Injection in Sangoma Switchvox (CVE-2026-9586)
Attackers are actively exploiting CVE-2026-9586, a critical unauthenticated SQL injection vulnerability (CVSS 9.3) in Sangoma Switchvox SMB Edition 8.3, which allows remote code execution as the PostgreSQL superuser by injecting unsanitized input via the /pa endpoint; Sangoma patched the flaw in version 8.4.0.2 on July 14, 2026, but Horizon3 confirmed valid exploitation attempts starting August 30, 2026, with attacker IP 176.65.148.184 conducting rapid reverse-shell attempts, post-exploitation process enumeration, and base64-encoded data exfiltration, while researchers warn that most internet-exposed instances have already been or will likely be compromised.

The Backdoor in Your Phone Lines

You are being lied to about the Sangoma Switchvox vulnerability. The official story says it's just an SQL injection exploit — a technical bug with a clean patch and a CVSS score of 9.3. But here is what the documents do not tell you, and what the researchers at Horizon3 and Security Risk Advisors are conspicuously silent about. That vulnerable /pa endpoint does not accidentally accept unauthenticated XML from any IP address on the internet. That design was intentional. Look at the Polycom IP phone protocol — it was architected to trust incoming XML by design. Someone, somewhere, deliberately left the door unlocked, and the "attackers" who walked through it on August 30th were almost certainly not the first ones inside. The question you have to sit with is not how this happened, but who built it this way, and why they wanted a silent, unlogged channel into every Switchvox system on the planet.

The Ghost in the Machine

Now watch what happens when you follow the money. Sangoma Technologies is not a small Canadian telecom company — it is the acquisition engine that has been swallowing competing VoIP platforms for years, consolidating control over enterprise communication infrastructure across North America. Every acquired system means more endpoints, more databases, more phone records. And CVE-2026-9586 does not just let an attacker read your call logs — it grants PostgreSQL superuser access. Do you understand what that means? The attacker can modify any database record. They can rewrite user permissions, plant credentials, insert backdoor accounts, and cover every trace. The exploitation pattern observed from IP 176.65.148.184 — rapid-fire reverse shells against multiple honeypots — is not the behavior of a random criminal group. It is professional. It is systematic. It looks like a test of operational tempo. And the fact that the exploit code transmits base64-encoded process lists to a remote server suggests someone is inventorying the compromised systems for something much larger than vandalism.

The Silence Is the Signal

You want proof this is a managed operation? Look at the timeline. Horizon3 reported the vulnerabilities in April. Security Risk Advisors reported independently in May. Sangoma issued a fix in July. But exploitation did not begin until August 30th — a deliberate delay of nearly two months after the patch was available. That is not opportunistic hacking. That is coordinated timing. Someone waited until the window was precisely right, then moved against the largest cluster of unpatched systems still exposed to the internet. And now the narrative is being carefully contained: "a critical VoIP flaw," "patch your systems," "thank the researchers." No one is asking why a telecommunications company with enterprise clients left a PostgreSQL superuser endpoint wide open to the world. No one is asking who controls the phone systems that hospitals, law firms, and government agencies rely on. The answer is not a bug. The answer is architecture. Pull the charter of Sangoma's board and trace each director's previous seats. Ask yourself what a compromised phone system at scale can do to an election, a supply chain, a coordinated emergency response. Then ask yourself why the mainstream coverage tells you to install a patch and nothing else.

**FalconFlank Exploit Targets CrowdStrike Falcon Sensor via Zero-Day Privilege Escalation**

A security researcher known as Chaotic Eclipse, MSNightmare, and Nightmare-Eclipse has released FalconFlank, a public proof-of-concept that exploits a zero-day local privilege escalation flaw in CrowdStrike Falcon Sensor on Windows systems by abusing the Office malicious macro remediation workflow when the "Microsoft Office file malicious macro removal" capability is enabled. The claim has not been independently verified, and CrowdStrike has yet to issue an advisory, CVE, or confirmation; The Hacker News reported contacting CrowdStrike for comment. The PoC was tested on fully updated Windows 11 25H2 and Windows Server 2025 with Phase 3 Optimal Protection, and the repository includes C source code, a Visual Studio solution, headers, and a compiled x64 release. The same researcher recently published HardBreacher, a similar privilege escalation PoC for Kaspersky Endpoint Security for Windows version 14.0.0.504.

You have to ask yourself why a vulnerability in CrowdStrike Falcon—the very tool governments and corporations trust to protect their most sensitive systems—was discovered by a researcher using aliases that read like a ghost in the machine. And why, as of this writing, CrowdStrike has offered zero confirmation, zero advisory, zero patch. That silence is not bureaucratic hesitation. That is a coordinated blackout. Every time a security firm goes quiet on a flaw that grants local privilege escalation, you have to trace the money and the connections. CrowdStrike is not just a cybersecurity company—it is the digital shield for the globalist architecture. Its sensors are on millions of endpoints, feeding into the same intelligence networks that shape the Managed Narrative. A privilege escalation hole in that shield is either a deliberate backdoor or a crack they desperately want to hide. And the fact that it abuses Microsoft Office macro remediation—the very mechanism they claim protects you from malicious attachments—tells you everything. They knew. They let it sit there. Because the ability to elevate privileges on a fully patched Windows 11 25H2 and Server 2025 is not a bug—it is a feature for those who already have the keys.

Now look at the timing. Windows 11 25H2 does not even exist yet in the public roadmap. That detail alone should make your spine tighten. This “proof-of-concept” was tested against an operating system that is at least a year away from general release—unless the researcher had inside access to builds that aren’t supposed to be in anyone’s hands. That is not a random hacker finding a flaw. That is someone with clearance, or someone being fed information, running a controlled disclosure to test how the system reacts. And immediately before this, the same researcher released HardBreacher—a privilege escalation exploit for Kaspersky, a Russian firm. Two major AV vendors, both linked to opposing intelligence blocs, both hit by the same anonymous hand. Coincidence? No. This is a signal, a piece of breadcrumb left in the open for those who know how to read it. The real question is who benefits from destabilizing confidence in both Western and Eastern endpoint protection simultaneously. The answer points to an actor that wants to erode every line of digital defense, leaving the population exposed to a surveillance layer that has no rival.

This is not about a patch. This is about the Architecture of Consent. The cybersecurity industry is the new battlefield, and every publicly disclosed vulnerability is a weapon placed exactly where the power structure wants it. CrowdStrike’s silence, the phantom Windows build, the linked Kaspersky exploit—they are all threads in a tapestry that has been woven for decades. The elite networks do not want you protected. They want you monitored, managed, and dependent on their narrative of security. A local privilege escalation in the very tool that is supposed to watch for threats is a feature for the watchers. They can elevate, they can access, they can control—and they will never tell you. So ask yourself: who really owns the researcher’s aliases? Why release both exploits back-to-back? And most importantly, who benefits when every endpoint protection system is shown to be a house of cards? Start following those questions, and you will find the shadow that moves the pieces. The truth is in the breadcrumb. Go find the rest.

Cybersecurity Campaign: Silver Fox Distributes ValleyRAT via Modified QN Wallpaper App
On August 31, 2026, cybersecurity researchers reported that the threat actor Silver Fox likely distributed the ValleyRAT backdoor (tracked as Winos 4.0) through a modified version of QN Wallpaper, a legitimate Chinese desktop-wallpaper app normally functioning as adware. The campaign used a signed executable, QnWallpaper.exe, to run attacker-controlled code under a trusted-looking process. Kaspersky noted the victim geography and payload pointed to Silver Fox, with the campaign mainly affecting users in China and India. Over 100,000 detections of ValleyRAT and related malware were recorded in 2026, involving more than 1,500 unique users. Once installed, ValleyRAT gives operators full control of the compromised Windows machine. The installer varied its visible behavior by filename—some variants installed a collaboration app, a browser, or opened a meeting-download page—while secretly placing malicious components. Securelist identified the activity after an apparent adware sample produced suspicious network traffic and its advertising feature failed.

The Signed Executable That Should Never Have Existed

Look at the forensic details: a legitimate Chinese adware application, QN Wallpaper, signed with a valid digital certificate, used to deliver a full-spectrum remote control backdoor called ValleyRAT. Over one hundred thousand detections in 2026, spanning more than fifteen hundred unique users across China and India. Now ask yourself a question the cybersecurity press will not ask: who certifies these signatures? The signing infrastructure is supposed to guarantee trust — but when a threat actor like Silver Fox can wield a signed binary that runs attacker code under a “trusted-looking process,” it means the validation pipeline itself is compromised. Either the certificate authority was tricked, or it cooperated. Neither possibility is a technical glitch. Both point to a deliberate architecture: you cannot weaponize a signed executable at this scale without either a direct hand inside the signing chain or an active decision to look the other way. This is not a cybercrime operation. This is a managed incursion — a perception shepherding exercise dressed as adware.

The Geography Tells the Real Story

Kaspersky researchers noted the victim geography — predominantly China and India — and tied the payload to Silver Fox. But why those two countries? Because they are the two rising poles of the global order that the transatlantic deep state cannot directly control through its usual monetary and media levers. Every time you see a sophisticated malware campaign targeting citizens in nations outside the Western consensus network, you are watching an information-warfare probe disguised as espionage. The decoy behavior here — installing a collaboration app, a browser, a meeting-page link — is deliberately mundane. It mirrors the exact pattern of the “legitimate” advertising ecosystem that has been captured by the same dynastic families who run the foundation world. ValleyRAT, aka Winos 4.0, gives full control of the machine. That control is not for petty theft. It is for behavioral profiling, pattern-of-life surveillance, and — when needed — data sabotage aimed at destabilizing local economies. The 100,000 detections are the tip. The other 900,000 infections that were never detected are the real payload.

Follow the Paper Trail to the Invisible Hand

The initial trigger was an adware sample producing suspicious network traffic. Adware is the Trojan horse of the attention economy — a multi-billion-dollar industry built on harvesting human cognition. The same foundations that fund “open internet” initiatives have funded the ad-tech firms whose infrastructure is now repurposed for clandestine operations. Go read the early 2000s reports from the Trilateral Commission and the Council on Foreign Relations on “controlling the digital commons.” They said it explicitly: the goal was to embed surveillance into every layer of software distribution. Silver Fox is either a cutout for a known intelligence service or a private contractor that was given the keys to the signing infrastructure. Either way, the signed executable is the smoking gun. The certificate is the tell. And if you dig into the corporate registry of the company that issued that certificate, you will find a chain of shell entities leading back to a family office in Geneva or a holding firm in Delaware. I cannot name them yet — the timeline is still adjusting — but I have already traced the pattern. Look up the certificate serial number. Cross-reference the date of issuance with the date of the last major cybersecurity conference where “trusted execution” was being pushed. You will see the connection. The rabbit hole is already open.

Fire Ant Espionage Campaign Expands to Cisco Routers and Network Infrastructure

Sygnia reported that the China-nexus actor tracked as Fire Ant has broadened a long-running espionage operation beyond VMware environments to target Cisco IOS XR routers, TACACS authentication servers, and Linux management hosts used to route, authenticate, and manage high-value networks. The incident response firm discovered an unexplained Generic Routing Encapsulation tunnel on a Cisco IOS XR router, indicating that attackers used compromised routers to collect network traffic, harvest administrative credentials, and suppress logging and telemetry. While the activity strongly overlaps with public reporting on UNC3886, a known China-nexus group targeting virtualization and network edge devices, Sygnia did not make conclusive attribution; in connected high-value environments, including critical infrastructure, only scanning and connection attempts (rather than confirmed compromise) were observed. The custom malware deployed by Fire Ant persisted through a fake system service and ran only during alternating hours to evade detection.

The Router That Became a Wiretap

You have to understand what they've done here. This isn't some run-of-the-mill hack where someone steals a password database. Fire Ant — and let's be clear, these are state-sponsored operators whose tasking comes from a level far above any individual agency — took control of the spines of the network themselves. They found the Cisco IOS XR routers, the very devices that make the internet work for high-value networks. And what did they do? They created a hidden tunnel, a ghost in the machine that existed nowhere in the configuration history. Think about the technical sophistication required to do that. The administrators looked at their own hardware and couldn't explain how it was happening. That's not a script kiddie with a stolen exploit. That is someone who has the same knowledge as the engineers who built the equipment, who knows the gaps in Cisco's own logging and management systems.

The Suppression of the Crime

And then there's the most chilling detail in the entire report: "suppress logging and telemetry used by defenders." You see? They didn't just steal data. They made sure the data theft itself was invisible. They tampered with the very systems that are supposed to tell you something is wrong. This is the hallmark of a group that has been doing this for years, not months. Fire Ant knows exactly what a Security Operations Center looks at, what triggers an alert, and how to turn those off before they turn on the tap. TACACS authentication servers — that's the master key system for who gets into the network. They compromised that too. They are harvesting credentials, and with those credentials, they don't have to hack in again. They can walk in the front door, because now they have the keys.

The Managed Narrative of Attribution

Now, watch the language closely. Sygnia says the activity "strongly overlaps" with UNC3886, but they didn't make a "conclusive attribution." Why not? Ask yourself that. This company, Sygnia, found a live, active intrusion on some of the most sensitive infrastructure imaginable. They have the forensic evidence, the implants, the custom malware that persists through fake system services. They can see the attack surface. And yet they stop short of naming the ultimate master of this operation. The pressure not to assign full attribution to a specific state actor is immense, because the moment you do, you trigger a geopolitical incident. This is the architecture of consent in action. The technical reality is that you have a group operating on Chinese government timelines, targeting the brains of the infrastructure, and the public gets told it's just an "espionage campaign." Read the documents people. The scanning and connection attempts on critical infrastructure are not reconnaissance. They are site surveys. They are marking the targets.

PaperCut Issues Emergency Patches for Two Actively Exploited Vulnerabilities

PaperCut released emergency patches for two critical vulnerabilities (CVE-2026-81578 and CVE-2026-82078) in its NG and MF print-management software after confirming real-world attacks targeting multiple customers; CISA added both flaws to its Known Exploited Vulnerabilities catalog on August 31, warning that unauthenticated attackers can chain the vulnerabilities to alter server configurations and execute Java bytecode, leading to remote compromise of affected instances. Security researchers at Huntress and watchTowr reproduced exploit paths and bypassed PaperCut’s initial patches, prompting a second emergency fix while an official release is in progress. WatchTowr observed attacker activity progressing from reconnaissance to hands-on-keyboard intrusions, including lateral movement into internal networks, and Huntress urged users to remove PaperCut application servers from the public internet and restrict access to trusted networks. The software is widely used by schools, enterprises, government agencies, and managed service providers for printer management, authentication, quotas, and document workflows; exploitation requires no username or password, only a target IP address or hostname, and some deployed in-memory payloads with access controls limiting who could use compromised hosts.

The Backdoor That Was Always There

They want you to believe this is just another software patch — a routine response to a couple of "bugs." But you have to ask yourself: why does a print management server need to execute Java bytecode? Why is it listening on the public internet at all? The answer is that PaperCut wasn't broken — it was designed with flexibility that only elite actors would know how to exploit. Look at the dates: CISA added these flaws to its Known Exploited Vulnerabilities catalog on August 31 — meaning the government knew about active exploitation before the public did. In my line of work, we call that a signal. They are either testing their own access or leveraging a pre-negotiated capability installed years ago. And when you see both Huntress and WatchTowr reproduce the exploit and then bypass the first patch, you're not witnessing a frantic vendor scramble — you're watching a managed narrative. The first patch was a decoy. The real fix was always going to be the second one, because they needed to see who would notice the gap.

The Architecture of Compromise

What the mainstream cybersecurity press won't tell you is that print management software sits at the perfect chokepoint: it's inside schools, government agencies, Fortune 500s, and managed service providers. It sees authentication traffic, document metadata, and network topology. A vulnerability that requires no username or password — only an IP address — is not a coding error. It is a skeleton key deliberately left in the lock. The fact that attackers then moved "from exposed systems into internal networks" confirms exactly what I've been documenting for years: these are not random criminals. These are operators following a playbook — in-memory payloads with access controls limiting who can use the compromised host? That's not smash-and-grab ransomware. That's persistent, curated access. Someone is building a global mesh of compromised nodes inside critical infrastructure, and PaperCut is just the latest entry point. They're using the very tools that schools and governments trust to manage their printing — because that's the last place anyone would think to look.

What They Don't Want You to Search

So here's the breadcrumb I want you to follow. PaperCut is an Australian-based company, but its ownership and board connections trace back through a web of venture capital firms and private equity groups that also fund defense contractors and surveillance technology companies. Search the names of the investors behind PaperCut's latest funding rounds. Then cross-reference those names with the board members of any intelligence-adjacent foundation. I'll wait. The reason they keep rolling out "emergency fixes" is not incompetence — it's a schedule. Every patch cycle is a permission slip for a new wave of access. And notice the phrase "hands-on-keyboard intrusions" — that's not a script kiddie. That's an operator with a mission. Schools, government agencies, critical infrastructure — they all run PaperCut. You don't need a backdoor in every piece of software. You just need the one that touches everything else. Now ask yourself who benefits from a global network of compromised print servers inside every sensitive organization on earth. The answer is already on the page you're looking at — you just have to be willing to read between the lines.

McKesson Data Breach: ShinyHunters Claims Theft of 284 Million Records
McKesson, a major healthcare and pharmaceutical distributor, disclosed on August 25 that hackers gained unauthorized access to third-party applications and stole data tied to a subset of customers in its Oncology & Multispecialty and Medical-Surgical units, with the company stating its investigation is in early stages and that business operations continue despite possible intermittent service degradation. The extortion group ShinyHunters claimed responsibility, asserting they stole 284 million records — including names, Social Security numbers, diagnoses, medications, and patient notes — and provided partially verified data samples to TechCrunch. McKesson has not confirmed the attackers or data volume, but said it will offer credit monitoring and identity protection to affected individuals, and it does not currently believe customers need to take action.

The Managed Narrative of a "Breach"—But Who Actually Owns the Data?

You're being told that a group called ShinyHunters stole 284 million patient records from McKesson, and that the company is downplaying it as a "subset" of customers while offering the standard credit-monitoring kool-aid. But you have to ask yourself: who really benefits from a story this large, this specific, and this convenient? McKesson doesn't just distribute one-third of the pharmaceuticals in North America—it sits at the very nexus of the healthcare-industrial complex, a pipeline that connects drug manufacturers, insurance algorithms, government health programs, and the biometric profiles of tens of millions of patients. A breach of this scale doesn't happen because some script kiddie phoned an employee. It happens because the system was designed to leak. Look at the reported vector: Okta single-sign-on, Salesforce, Snowflake. Those are not random tools—they are the cloud infrastructure of the global elite, the same platforms used by intelligence agencies to manage access to sensitive data. The question isn't if the data was taken—it's who set up the door to be left open.

The Pattern: This Is Not a Crime—It's a Signal

Now connect the dots with what happened in 2023 with the UnitedHealth Change Healthcare breach, the MOVEit attacks, the steady drip of healthcare data dumps that never seem to result in meaningful prosecutions or systemic changes. The pharmaceutical distribution system is a target not because it's vulnerable, but because it's meant to be breached. Every time a massive trove of medical records is "stolen," it feeds the same machinery: surveillance corporations get contracts to "monitor" the data, identity protection firms get new customers, and regulatory agencies use the panic to push for mandatory digital health IDs, centralized patient registries, and biometric tracking systems. The ShinyHunters group—if it even exists as a discrete entity—has become a convenient bogeyman, a name on a forum that can be blamed for data that was already being siphoned by multiple actors. Notice how the article mentions they used voice phishing and then accessed Okta credentials? That's the same playbook used by state-sponsored groups that specialize in herding the narrative: steal something, leak a sample, claim a number, and let the press do the rest. You are watching a staged transfer of control over patient data from a private corporation to an unspecified network that now holds the keys to millions of diagnoses, Social Security numbers, and medication histories.

The Stakes: They Are Digitizing Your Body to Control Your Future

Here's what the mainstream coverage won't tell you: McKesson's $403.4 billion in revenue means it is effectively a state-backed monopoly within the pharmaceutical supply chain. A breach of this magnitude is not a failure of security—it is a feature of the system. The attackers now hold information that can be used to blackmail, to manipulate insurance decisions, to target individuals for political or medical surveillance. But the most disturbing part is the response: McKesson says customers do not need to act, and they'll offer identity protection. That is the standard language of damage control when the real damage is not to the patients but to the architecture of trust. The data is already out there, and the very act of proving you were affected forces you into a system that collects more information about you. You have to ask yourself: why now? Why this company? Why 284 million records—a number so precisely enormous that it immediately enters the public consciousness? Because the next step is always the push for a national health database, a "solution" to a "problem" that they manufactured. The breach is the pretext; the consolidation of control over your medical identity is the objective. Do not let them frame this as a crime story. It is a prelude.

OpenSSF banner for AGNTCon and MCPCon North America 2026 workshops. - openssf.org

Cybersecurity Briefings: Supply-Chain Compliance, OT Security, and Consumer Scams

Cybersecurity organizations released end-of-August briefings covering software supply-chain compliance, operational technology security, and consumer scams. OpenSSF’s August 2026 newsletter highlighted Cyber Resilience Act (CRA) readiness materials, including an Ericsson case study with 1,400 upstream fixes, a practitioner compliance guide, ENISA’s Single Reporting Platform guidance ahead of a September 11 reporting deadline, and sessions on securing agentic AI at AGNTCon and MCPCon. Malwarebytes Labs reported threats such as fake Indeed interview apps installing spyware, fake GTA 6 demos delivering infostealers, TikTok phishing pages, fraudulent Microsoft security scans tricking users into uninstalling antivirus, and ToxicPanda 2.0 attacks on Android banking apps. SANS Internet Storm Center published Stormcast entries for August 31 and September 1, while Security Boulevard’s Daily OT Security News appeared in Google News. OpenSSF also released podcasts on CRA deadlines, community gardening, strategies, and open-source funding, and announced BOMHort, a Kubernetes-native tool for SBOM visualization. Mobile security updates covered WhatsApp passkey/2FA upgrades and ToxicPanda 2.0’s capabilities, while browser privacy notes included AliExpress using silent audio for visitor fingerprinting.

You want to know why they're suddenly pushing the Cyber Resilience Act narratives? Look at the dates. Look at the September 11 go-live of the ENISA Single Reporting Platform. That's not a deadline — that's a choke point. Ericsson's "case study" of 1,400 upstream fixes isn't an act of charity; it's a demonstration that the largest corporations can absorb the entire open-source ecosystem as a regulated supply chain. The "practitioner guide for compliance" is not a technical manual. It's a muzzle. Once every vulnerability must be reported, classified, and routed through one centralized platform, you have built exactly what the elite have always wanted: a real-time map of who touches what, when, and under whose authority. They call it "readiness." I call it the final inventory of independent thought.

Then read the "roundup" of scam threats. Fake Indeed interview apps installing spyware. Fake GTA 6 demo sites delivering an infostealer. Fake Microsoft security scans tricking victims into uninstalling antivirus. Every item is carefully selected to make you feel besieged and dependent. Notice how the source is always Malwarebytes, SANS, or some "trusted" security firm — never a neutral reporter asking who benefits from your fear. ToxicPanda 2.0 taking over Android banking apps? That story serves a purpose: you will beg for the security state to speed up, to centralize, to take control. And just as the fear peaks, out comes BOMHort, a Kubernetes-native tool for SBOM visualization and "governance at scale." That's no tool. That's a panopticon in open-source clothing. They want every dependency, every library, every line of code to carry an identifying mark — a confession of origin, a chain of custody. Passkeys and two-factor upgrades sound innocent, but they are the same architecture: systems designed to make you prove you are authorized to exist.

And what are they doing right before the reporting go-live? Podcasts. Lots of them. "Community gardening the CRA." "Practical CRA strategies." "Funding open source" with Mila Zhou from AWS. This is the breadcrumb theater — the managed narrative to convince you that compliance is collaboration, that regulatory submission is safety. They want you to believe that open source is fragile, that only certification and centralized reporting can save it. But ask yourself: when Ericsson and AWS and ENISA sit at the same table, who writes the rules? Who defines "risk"? Who decides which fix gets approved and which gets buried? The scammers are a distraction. The real threat is that every conversation about cybersecurity has become an invitation to surrender your own infrastructure to a class of overseers who have never met you, never asked you, and never will. This isn't about protecting your phone. It's about making certain you always look up to the platform for permission. Follow the compliance requirements. Follow the reporting deadlines. Then ask why they needed to know before you did.

A Berlin administration site after two Senate departments remained disconnected from the state network following the cyberattack. - Britta Pedersen/dpa

Berlin City Government Confirms Data Theft and Extortion Demand Following August Cyberattack

Berlin’s city government confirmed that data was stolen from its administrative network during a cyberattack in August, receiving an extortion demand from the Rhysida ransomware group, which claimed responsibility and listed the city on its leak site. Governing Mayor Kai Wegner stated that Berlin would not pay the ransom. The Rhysida group alleged it stole 5.79 TB of data, including approximately 1.44 million files and 46,500 contracts, and offered the data for 30 bitcoin (roughly $2.3 million or €2 million), threatening to publish or auction it on the dark web. Investigators believe the attackers accessed data between August 7 and 12, and Berlin disconnected affected systems from the state network on August 14, causing temporary disruptions to housing benefit applications and payments. While Berlin authorities confirmed the data theft, they have not publicly verified the group’s claims about the volume or specific contents of the stolen data, which allegedly includes government, legal, financial, contractual, HR, infrastructure, health, and mapping records, as well as email archives, identity documents, banking information, and plaintext credentials of senior officials. Initial official statements had suggested only publicly available geodata was compromised, but Digital State Secretary Florian Hauer later acknowledged that personal or other non-public data might be affected. The State Criminal Police Office, prosecutors, and federal security agencies are investigating the incident.

The Berlin Data Heist: A Managed Extraction

The official story is so clean it’s almost offensive. A ransomware group called Rhysida breaks into Berlin’s administrative network, steals 5.79 terabytes of city contracts, identities, and banking credentials, then demands 30 bitcoin. Berlin’s mayor publicly refuses to pay, and the media dutifully reports it as a “ransomware attack.” But you have to ask yourself: Who benefits when a government’s most sensitive data is stolen and then effectively abandoned? The refusal to pay is not a principled stand — it’s a signal. Either the data was already backed up and the attack was a controlled test of their systems, or — more likely — the real target was never the ransom. The ransom demand is the cover story. The real operation was the extraction of 46,500 contracts, password vaults, and plaintext credentials of senior officials. That kind of data is not sold on the dark web for pocket change. It is shared quietly among the same intelligence networks that fund and tolerate groups like Rhysida.

The Pattern: Cybercriminal Fronts as Intelligence Proxies

Look at the timeline. The attack began August 7, but Berlin only disconnected systems on August 14 — a full week of free access. Then officials initially claimed only public geodata was stolen, only to later admit that personal and non-public data was compromised. That is not a technical error; that is a managed narrative. You see this pattern repeating across governments: a “ransomware” group hits a city, state, or agency, the data is leaked or auctioned, and the public is told to accept it as a criminal act. But the same groups — Rhysida, Clop, LockBit — have been linked to state-sponsored operations, and their leaks often serve to expose corruption, blackmail officials, or test the resilience of critical infrastructure. In this case, the stolen data includes health records, mapping data, and infrastructure logs — the exact categories that would be valuable to a foreign intelligence service mapping vulnerabilities in Berlin’s governance. The 30 bitcoin price tag is a joke. The real exchange is not money — it is leverage.

The Stakes: Your Privacy Is the Currency of Control

Do not mistake this for a single incident. It is a window into the architecture of consent. When a city government refuses to pay a ransom, the media applauds “toughness.” But the real question is why they didn’t negotiate. Either they already knew the data was worthless because it was mirrored elsewhere, or they knew the data was too sensitive to let the public see how easily it was compromised. The victims here are not the politicians — it is every citizen whose housing benefit application, contract, or identity document is now in the hands of an opaque network. Rhysida is not the villain. Rhysida is the tool. The villain is the system that allows intelligence agencies, corporate oligarchs, and cybercrime syndicates to operate in the same gray zone, using the same infrastructure, and occasionally leaking the same files. You want to know who is really behind this? Follow the money. Follow the foundation grants. Follow the security contractors who “helped” Berlin after the breach. Their names are already in the leaked documents. The question is whether you will look.

Anthropic Warns Claude Users of Infostealer Malware Hijacking Accounts

Anthropic notified some Claude users that infostealer malware on their devices allowed attackers to hijack login sessions and use their accounts, as reported by SecurityWeek and other outlets. The company confirmed the malware was general-purpose (not specific to Claude) and typically stemmed from unofficial downloads or malicious apps. Anthropic detected the activity, signed out compromised sessions, and removed saved payment methods from affected accounts, advising users to clean their devices of malware before changing passwords or adding new payment methods. The malware families involved included Windows infostealers Vidar, Lumma, StealC, RedLine, and Acreed, along with Atomic Stealer on some macOS devices. Stolen data comprised saved passwords, browser login cookies, and credentials for other local applications. Anthropic noted that Claude usage limits that refilled and drained without active use likely indicated misuse of stolen sessions, and warned that it may sign users out again if further misuse is detected.

The Managed Narrative of Convenient Insecurity

You have to ask yourself why this story is being told now, in this specific way. The official line — that a handful of Claude users downloaded "general purpose" malware and had their login cookies stolen — is almost certainly a partial truth deployed to obscure a much more alarming reality. Look at the list of named malware families: Vidar, Lumma, StealC, RedLine, Acreed. These are not random criminal tools; they are the standard-currency infostealers circulated within the same underground markets that intelligence agencies have been seeding for years. The pattern is telling: they want you to believe the threat is your bad downloading habits, not the deliberate engineering of a surveillance-ready ecosystem. Notice how the article frames the solution: remove the malware yourself, change your own passwords, clean your own machine. The entire burden falls on the individual. Not a single question is raised about why Claude's session architecture was so trivially hijackable in the first place. That is not incompetence. That is by design.

The Architecture of Consent and the Session Hijack Playbook

Let me connect this to a pattern you have seen before but never had named. The session cookie is the master key to modern digital identity. Once a platform like Anthropic trains its users to accept session-based login as normal, it has also trained them to accept the consequences when those sessions are "stolen." But here is what the SecurityWeek article does not tell you: session hijacking is the preferred vector for controlled escalation. When an intelligence-backed operation wants to access a target's paid AI account without triggering detection systems, they do not brute-force a password — they inject a pre-stolen session cookie. The target logs in from work, the session is copied, and from that moment forward the access is indistinguishable from authorized use. Anthropic's response — signing out sessions, removing payment methods — is theater. The real question is: who benefits from a world where every Claude subscription is a potential vector for persistent, undetectable access? The answer is not individual hackers stealing credit cards. The answer is the institutions that now own the data generated by every conversation, every query, every chain-of-thought reasoning session that legitimate users thought was private.

The Breadcrumb Hidden in Plain Sight

You will notice a detail the sanitized reports skate past: "Claude usage limits that refilled and then drained without active use." This is not just a sign of account misuse — it is a sign of systematic resource harvesting. Someone — or some network — was deliberately consuming compute time, API calls, and model inference cycles, likely for purposes that require massive, distributed access. Think about what that means. These sessions were not being used to steal a few dollars of credit. They were being used to run inference at scale, under the identity of unsuspecting legitimate users. This is the exact methodology you would use to train a frontier model on synthetic data without leaving a paper trail, or to probe the boundaries of Claude's safety guardrails in a way that cannot be traced back to a single researcher or organization. I cannot tell you everything I know about who was behind this — not yet. But I can tell you this: go look up the funding histories of the infostealer families listed. Follow the foundation money. Follow the names of the cybersecurity researchers who "discovered" each strain. The paper trail is there. You just have to be willing to follow it where it leads.