Europol announced on June 12 the dismantling of AudiA6, a cryptocurrency laundering service that marketed itself to ransomware gangs and other cybercriminals as a fast, reliable way to convert stolen cryptocurrency into clean funds. The service, operational since 2021, processed more than €336 million across approximately 10,333 bitcoin deposited. Fees charged to customers ranged from 3% to 10%, with clean funds delivered within approximately one hour. AudiA6 used thousands of fraudulent exchange accounts created with stolen or purchased identities to move funds through the laundering chain.
The coordinated action took place on June 10, 2026. Two alleged administrators, Ruslan Igorevich Tkachuk, 37, a Ukrainian national, and Alexander Vladimirovich Ledenev, 25, a Russian national, were arrested in Georgia. Authorities seized more than 30 servers and 25 domains, froze €692,000 in cryptocurrency, and seized a further €86,000 in cryptocurrency. Telegram accounts used by the network were also blocked. The US Department of Justice unsealed charges in the Eastern District of Pennsylvania against both individuals for conspiracy to launder monetary instruments and sting money laundering, each carrying a maximum sentence of 20 years.
The investigation began with the September 2025 arrest in Poland of a separate Ukrainian suspect linked to the network. Analysis of devices seized at that arrest gave investigators the broader network. Europol’s analysis linked AudiA6 to more than 15 ransomware operations and major cryptocurrency theft schemes. The operators also ran Dark2Web, a dark web forum used to connect ransomware groups with affiliates and service providers across the criminal ecosystem. Both services were simultaneously taken down.
- No immediate technical action. Internally, use this as a reference point in board-level discussions about ransomware payment decisions. Ransom payments flow through exactly this kind of laundering infrastructure, and law enforcement's growing ability to trace and seize those funds is an additional argument against payment.
Lumen’s Black Lotus Labs published a detailed analysis of the JDY botnet on June 10, documenting its growth from approximately 650 active nodes in January 2024 to over 1,500 compromised devices today. JDY was first identified in December 2023 as a cluster within KV-botnet, the network used by Volt Typhoon and disrupted by the FBI in early 2024. JDY survived that takedown, adapted, and has since operated as an independent capability.
The botnet compromises SOHO and IoT devices including hardware from Cisco, Araknis, Mimosa Networks, Ubiquiti, DrayTek, Hikvision, and Linksys across MIPS and MIPSEL architectures. Once compromised, devices are used as distributed scanning and fingerprinting nodes rather than as direct exploitation tools. JDY conducts service discovery, banner grabbing, TLS certificate harvesting, and protocol fingerprinting at scale. The scanning output is collected and analysed centrally, with command and control managed through hidden Tor services. In some cases, compromised devices are also managed using the open-source Platypus reverse shell framework.
The botnet’s primary focus is the United States. Of the IP addresses JDY scanned, the largest share belonged to networks operated by the US military and associated entities. Black Lotus Labs observed a sharp increase in scanning of Fortinet devices within hours of the public disclosure of CVE-2026-35616 on April 5, 2026, confirming the botnet’s near-real-time responsiveness to new vulnerability disclosures. Black Lotus Labs assesses that JDY continues to support multiple China-nexus APT actors based on its victimology patterns and historic links to KV-botnet.
- Audit network edge devices in your environment: routers, cameras, and IoT hardware from Cisco, Ubiquiti, DrayTek, Hikvision, and similar vendors. Verify firmware is current and compare against Black Lotus Labs’ published IOCs for JDY-compromised device indicators.
- For internet-facing edge infrastructure, establish a same-day patch target for critical vulnerabilities at the network perimeter. JDY scanning begins within hours of disclosure; the patch window is shorter than the standard enterprise cycle.
- Review whether SOHO and IoT devices in your environment are in scope for your existing vulnerability management programme. If they are not, this is the case for including them.
Google released an emergency Chrome stable channel update on June 8, 2026, addressing 74 security vulnerabilities including CVE-2026-11645, a high-severity out-of-bounds read and write vulnerability in V8, Chrome’s JavaScript and WebAssembly engine. Google confirmed that an exploit for the vulnerability exists in the wild. A security researcher known as 303f06e3 reported the flaw on April 27, 2026, and received a $55,000 bug bounty for the discovery.
The vulnerability allows a remote attacker to execute arbitrary code within the browser’s sandbox by convincing a user to visit a specially crafted HTML page. Google has not disclosed the specific attacker, campaign, delivery infrastructure, or exploit chain, a standard practice when actively exploited browser vulnerabilities are being patched to limit information available to attackers while updates propagate. CISA added CVE-2026-11645 to its Known Exploited Vulnerabilities catalog on June 9 and directed federal agencies to remediate by June 23.
The flaw affects Chrome versions prior to 149.0.7827.103 on Windows and macOS, and prior to 149.0.7827.102 on Linux. Because Chromium forms the foundation for several other browsers, including Microsoft Edge and Opera, users of those browsers should verify that their browser vendor has shipped a corresponding update addressing the same V8 engine version. Chrome updates take effect when the browser is restarted; the update being installed does not mean the patched version is running.
- Push the Chrome 149.0.7827.102/.103 update through endpoint management to all managed endpoints before the June 23 CISA deadline.
- Verify running Chrome versions, not installed versions. Chrome updates require a browser restart to take effect. Confirm that the version shown in chrome://version is 149.0.7827.102 or later on each endpoint.
- For Microsoft Edge deployments, verify that Microsoft has shipped a corresponding Chromium engine update and that it has been applied. Check the Edge release notes for the V8 engine version included in the current stable release.