BleepingComputer reported on 8 October 2026 that Raheim Hamilton, 30, who co-created and ran the Empire Market dark web marketplace from August 2017 until it went offline in 2020 amid extortion DDoS attacks and exit-scam claims, has been sentenced to 40 years in federal prison, citing the US Attorney's Office for the Northern District of Illinois. Empire facilitated more than 4 million transactions worth about US$430 million; drugs made up nearly US$375 million, but the site also sold counterfeit currency, stolen account credentials, hacking tools and personal information. At its peak in August 2020 it had about 1.68 million registered users, over 5,000 vendors and nearly 360,000 buyers. Hamilton pleaded guilty in January and agreed to forfeit three Virginia properties, about 1,230 bitcoin and 24.4 ether; co-defendant Thomas Pavey ('Dopenugget') pleaded guilty last year and is due to be sentenced later this month. Authorities seized about US$75 million in cryptocurrency when the pair were charged in July 2024. Primary: US Department of Justice (USAO Northern District of Illinois); wire: BleepingComputer.
US Attorney's Office, Northern District of Illinois — Co-creator of dark web marketplace sentenced to 40 years in federal prison
Socket and StepSecurity reported on 8 October 2026 that version 0.5.144 of tensorlake, the TypeScript SDK for Tensorlake's sandboxes for running LLM-generated code (about 12,000 weekly downloads), was malicious. StepSecurity says someone pushed eight commits straight to the main branch of tensorlakeai/tensorlake under a maintainer's name from 01:20 UTC on 7 October, and the project's own release workflow published 0.5.144 to npm at 01:12 UTC on 8 October, so the package carries a genuine npm provenance attestation. Socket flagged it about 11 minutes after release and it has since been pulled from npm. A preinstall hook runs lib/setup.mjs, which skips CI, downloads the Bun runtime and runs an obfuscated payload (lib/Math_Symbol.js) that collects GitHub and npm tokens, cloud keys, Kubernetes and Vault secrets, SSH keys, saved browser logins and config files for AI coding tools. Data goes to a public GitHub repository created in the victim's account (description 'Shai-Hulud: Here We Go Again') or to a server found through an Ethereum contract. With a stolen npm token the worm republishes the victim's packages with itself added; with a GitHub token it commits .claude/settings.json and .vscode/tasks.json files so it runs again when a project is opened in Claude Code or VS Code. It also installs a gh-token-monitor service that checks the stolen token every 60 seconds for up to 24 hours and deletes the user's home directory (or Windows profile) if the token stops working. The loader and payload names match the August ChainDrop compromises of keyv and cacheable. Primary: Socket and StepSecurity; wire: The Hacker News.
Socket — Tensorlake npm SDK compromised in ChainDrop Shai-Hulud credential-stealing attack (8 Oct 2026)
St Andrew's Hospital, a private hospital in Adelaide, said on Thursday 8 October 2026 that it had been investigating a breach of personal information affecting "a group of individuals". Chief executive Angela McCabe said the investigation had progressed far enough for the hospital to contact affected people directly, in line with its regulatory obligations, and that they had been given information on how to protect their personal information. The hospital says it has notified the Office of the Australian Information Commissioner (OAIC) and the Australian Cyber Security Centre, and is working with government agencies to apply extra measures to detect and prevent suspicious and fraudulent activity. The number of people affected, what kind of information was involved and how the breach happened have not been disclosed. South Australian Premier Peter Malinauskas said the state government expected to be briefed later on 8 October, including on whether anything criminal had occurred. Wire: ABC News 8 Oct; no hospital web notice found at the time of this check.
ABC News — 'Group of individuals' impacted by data breach at SA hospital (8 Oct 2026)
The US State Department's Rewards for Justice (RFJ) programme is offering up to US$10 million for information on Zhang Yu, a Chinese national it describes as a director at Shanghai Firetech Information Science and Technology Company working at the direction of China's Ministry of State Security Shanghai State Security Bureau. RFJ says that from early 2020 Zhang and his partner Xu Zewei, then general manager at Shanghai Powerock Network, gained unauthorised access to COVID-19 research at US universities and stole information from immunologists and virologists, and that in 2021 the pair exploited Microsoft Exchange Server flaws as part of the HAFNIUM mass-intrusion campaign, with victims including a US university and a law firm. Xu was arrested in Italy and extradited to the US in April 2026; Zhang remains at large. Cybersecurity News reported the offer on 8 October, citing the FBI Cyber Division; the RFJ page itself carries no date. The charges are allegations, not proof of guilt. Primary: Rewards for Justice.
Rewards for Justice — Zhang Yu (SSSB) (undated reward page, reported 8 Oct 2026)
Japan's National Police Agency (NPA) said in a press release dated 8 October 2026 that Germany had announced the arrest of a Russian national believed to have led the Qilin ransomware group, which has hit companies around the world, and that Germany's announcement mentioned the Japanese police's contribution. According to the NPA, after the suspect, for whom Germany had obtained an arrest warrant over a ransomware attack in Germany, arrived in Japan, the Kanto Regional Police Bureau's cyber special investigation unit and the prefectural police concerned worked with the Ministry of Justice, the Tokyo High Public Prosecutors Office and Germany to detain him on a provisional detention warrant under Japan's extradition law and then hand him over to Germany. The NPA says the same police units had also investigated ransomware cases in Japan in cooperation with Germany. The suspect has not been named. Updated 9 Oct 2026 (BleepingComputer, 11:38 pm Perth): BleepingComputer reported that Germany has arrested the suspect, a Russian national believed to be a leading member of Qilin, after his extradition from Japan earlier in October; that the NPA said he was detained after arriving in Japan as a tourist; and that Japanese media had reported the arrest earlier that week, citing internal sources. BleepingComputer says Qilin is a ransomware-as-a-service operation that emerged in August 2022 under the name Agenda and has targeted more than 2,350 known organisations in 62 countries, including Nissan, Asahi, Lee Enterprises and Australia's Court Services Victoria; that it more recently hit the US ATF and has been linked to the exploitation of Check Point VPN zero-days and Palo Alto VPN n-day flaws. Correction (26 Oct 2026): this card was first based on a SecurityWeek report (7 October) that this desk does not link. Details that only that report gave have been removed: the suspect's age, his detention in Osaka in May 2026, the 2 October handover date, the September 2024 attack on a logistics company, the ransom of more than US$160,000, the Synnovis attack, a 2025 leak-site count and CVE-2026-50751. The card now rests on the NPA press release and BleepingComputer, and its date has moved from 7 to 8 October 2026, the date of the NPA release. (source: National Police Agency of Japan; BleepingComputer) Correction (26 Oct 2026): removed a count of victims listed on Qilin's leak site since June; this desk does not publish leak-site claims. (source: BleepingComputer)
National Police Agency of Japan — press release on Germany's arrest of a Russian ransomware suspect (8 Oct 2026, Japanese)
Morphisec (Shmuel Uzan, 7 October 2026) documents VulcanRAT207.A, a multistage Windows intrusion that starts as a WhatsApp attachment: a ZIP carrying a financial-document lure and Statement.exe. The outer executable is NRV2E-packed; after unpacking, the loader screens the host (disk, display, memory, CPU, event logs, Registry, VM markers, security products and timing checks), attempts privilege elevation, restores a clean ntdll.dll to drop user-mode hooks, and injects an importless downloader into the LocalSystem Task Scheduler process using PoolParty Variant 7 (thread-pool IoCompletion), so later stages inherit a SYSTEM token. The shellcode beacons over HTTP to 61[.]18[.]208[.]27:8888, validates a 0x0207 magic header, and receives a deployment bundle. A reflective loader maps a Deployment DLL that (1) installs GoFly64.sys — a legitimately signed Chinese network-filter driver — to terminate selected Baidu security processes, (2) writes a persistent Vulkan side-load package under C:\Program Files\Common Files and a scheduled task that later starts a signed VulkanInfo binary loading attacker-controlled vulkan-1.dll / vulkan-1.bin, and (3) launches the WebSocket RAT in memory for system data collection, command execution, file management, screen capture, keylogging, local account changes and further payloads. Morphisec published SHA-256 and network indicators for the Statement.exe / VulcanRAT207.A chain. No Australia-specific victims were named. Primary: Morphisec (7 Oct); wire: Cybersecurity News (12 Oct).
Morphisec — From WhatsApp to SYSTEM: Inside the VulcanRAT207.A Intrusion Chain (Shmuel Uzan, 7 Oct 2026)
Huntress said on 7 October 2026 that since 10 September it has seen a phishing campaign that hosts its lure on Microsoft's real Power BI service so the first link gets past mail filters that trust the domain. Outlook phishing emails linked to a public report on app.powerbi.com showing a blurred form and a 'Download Reference' button. Huntress says attackers build these by publishing a dashboard from an account they control, often compromised or disposable, and sharing it publicly. No Power BI software flaw is involved. The button opened attacker pages (for example dailylifeproject[.]site and burnsworth[.]site) that fingerprinted the visitor (operating system, browser, screen size, automation signs, ISP and location), sent the details to a Telegram bot, allowed only Windows desktops and filtered out Microsoft or unknown ISPs, and redirected failures elsewhere. After a few seconds a script clicked a hidden link to download ScreenConnect.ClientSetup.exe from one attacker ScreenConnect tenant, with a different guest-access token for each lure. That first rogue client then installed a second ScreenConnect client tied to separate infrastructure (onthegotree[.]site), so removing one left access in place. In one incident a CMD file ran SCAutoFix.ps1 to install the second client and remove the first, the attackers ran a defence-evasion tool (HideUL_x64.exe), and a scheduled task, SCAutoRepairEvery2Min, re-ran the script every two minutes. Huntress saw a handful of endpoints hit by this delivery chain, and a retrospective hunt found the same unique ScreenConnect client and configuration on 22 more endpoints in separate incidents. Huntress says its SOC stopped the activity before it went further. Separate from the MSP360 and CSuite RMM phishing campaigns already on this desk. Primary: Huntress (7 Oct); wire: Cybersecurity News (12 Oct).
Huntress — Phishing campaign abuses Microsoft Power BI to deploy rogue RMMs (Sarah Reddish, 7 Oct 2026)
Searchlight Cyber researcher Kevin Gervot published a write-up on 7 October 2026 of two flaws in Discourse, the open-source forum platform Searchlight says powers more than 22,000 communities, including OpenAI, Atlassian and Cloudflare. Both were reported to Discourse on 9 June 2026 and affect default configurations. First, the color_scheme_id (and dark_scheme_id) cookie was written into a page tag without escaping and was not part of the anonymous page-cache key, so a single unauthenticated request could poison the cached page and run attacker JavaScript for every anonymous visitor, getting past Discourse's nonce-based Content Security Policy (CVE-2026-55674, CVSS 3.1 9.3). Second, a Trust Level 0 account, the lowest user level, could read files from the server through the profile picture upload. ImageMagick's policy blocked PostScript but still let Ghostscript handle files with a .pdf extension. Searchlight padded a JPEG so jpegoptim took about 25 seconds to process it, then used Ghostscript file operators that still work under its -dSAFER sandbox to swap the temporary file before ImageMagick computed the image's dominant colour. ImageMagick's MSVG coder then ran a Magick Scripting Language file that read a local file and saved it as an image, and Discourse handed it back as a normal upload URL (CVE-2026-55420). No Ghostscript zero-day was needed. Searchlight stopped at file read, but warns that reading Rails secrets such as secret_key_base could lead on to code execution. Discourse's CVE record for 55420 is titled remote code execution via PDF uploads, rates it CVSS 3.1 7.5 and says it needs certain non-default configurations. Discourse fixed its hosted sites on 15 June and published the ImageMagick fix on 30 June and the cache fix on 28 July. The fix adds a default-deny ImageMagick policy that blocks all delegates (no Ghostscript) and allowlists only the coders Discourse needs, and makes the colour-scheme cookies strict integers that are part of the cache key. This is separate from Hacktron's libheif research on this desk. No exploitation has been reported. Wire: Cybersecurity News 12 Oct.
Searchlight Cyber — A JPEG, a Race, and a Ghost: Breaking Discourse's Image Pipeline (Kevin Gervot, 7 Oct 2026)
AWS security bulletin 2026-128-AWS (published 7 October 2026, US Pacific time; early 8 October Perth) says missing authorisation checks in Amazon Athena engine version 3 request handling could have let an authenticated user read limited query metadata from other AWS accounts, namely AWS account identifiers and SQL statement text. AWS says query results, credentials and Amazon S3 data were not affected, that it fixed the issue on 1 September 2026, and that it has confirmed no customer metadata was accessed. No customer action is required. AWS credits Oren Yomtov of Act Security through coordinated disclosure. The AWS-issued CVE record rates it CVSS 3.1 7.7 (scope changed, high confidentiality impact). It is a cross-tenant flaw in a managed service, so there is nothing to patch on the customer side.
Microsoft told Microsoft 365 admins on 7 October 2026 (Message Center MC1490905) that Defender for Office 365 is extending Teams URL protection to links hidden inside QR codes. After a message is delivered, Defender extracts URLs from QR code images, checks them, and puts a warning on the affected message in both internal and external chats when a link is malicious. Organisations with Defender for Office 365 Plan 1 or Plan 2 and zero-hour auto purge (ZAP) for Teams turned on may also have eligible malicious internal messages blocked. URLs taken from QR codes will show up in the Advanced Hunting MessageUrlInfo table with UrlLocation set to QRCode. The feature is part of existing Teams URL protection and needs no end-user setup; general availability runs from early October to early November 2026. QR code phishing hides a malicious address in an image so text-based link scanning misses it. Sources: Microsoft 365 Message Center (public archive copy); Microsoft Learn; wire: Cyber Security News 10 Oct.
MC1490905 — Defender for Office 365: post-delivery protection for malicious QR codes in Microsoft Teams (published 7 Oct 2026; Message Center archive copy)
A researcher writing as m00dy published findings on 7 October 2026, coordinated through CERT/CC (VU#765030), and CVE-2026-93034 was published on 8 October for SGLang, a widely used serving engine for large language models. SGLang's processes pass internal messages over ZeroMQ. By default they use Python Pickle (SGLANG_USE_PICKLE_IPC=true), which can run code while loading data; operators can switch to MessagePack, but the MessagePack path still accepts a PickleWrapper record and immediately unpickles it without a type allowlist or authentication. On a stock v0.5.18 service running a real model across two GPUs, an unauthenticated peer on a second machine got its code to run inside the detokenizer process, with the setting both on and off. In the default single-node layout the receiver is local to the host; it becomes reachable over the network when data-parallel attention is enabled with a non-loopback --dist-init-addr. Source inspection found the same code in v0.5.20 and main on 1 October; the researcher had not assessed v0.5.21 (released 2 October), so no fixed version is confirmed. CVSS 3.1 9.8 (CERT/CC). No exploitation reported. Primary: researcher write-up and CVE record.
m00dy — Disabling Pickle did not remove Pickle (SGLang, CVE-2026-93034 / VU#765030; 7 Oct 2026)
IBM published a security bulletin on 7 October 2026 for IBM Security Verify Access 10.0 to 10.0.9.2 and IBM Verify Identity Access 11.0 to 11.0.3, the access-management and reverse-proxy gateway (formerly ISAM/WebSEAL) many organisations put in front of web applications for single sign-on and multi-factor login. The worst issues, CVE-2026-78401 and CVE-2026-78406 (both CVSS 9.8), let a remote attacker with no login run arbitrary code through deserialisation of untrusted data (CWE-502). The bulletin lists 22 CVEs in all. It also covers CVE-2026-16916 (9.1, authenticated code execution through a protection mechanism failure in the appliance), CVE-2026-17189 (8.2, reflected cross-site scripting), CVE-2026-19878 (6.5, bypass of extra authentication workflow steps) and denial-of-service, log-forgery and local management interface flaws. Appliance and container editions are both affected. IBM lists no workarounds and no exploitation. Primary: IBM.
IBM — Security Bulletin: vulnerabilities addressed in IBM Verify Identity Access and IBM Security Verify Access (7 Oct 2026)
