Morphisec

𝟞𝟿𝇶𝇰𝇹𝇴 𝟞-𝐂𝐖𝐬𝐢𝐧𝐞𝐬𝐬 𝗦𝘮𝘴𝘷𝐞 𝐂𝗳𝗘-𝟙𝟘𝟙𝟖-𝟑𝟘𝟑𝟛𝟖𝟛 (𝐂𝗳𝗦𝗦 𝟟.𝟘): Active exploit probing against Oracle EBS began October 27 — one day after Oracle’s October CPU patched this unauthenticated SQL injection chain. The flaw targets the Thin Client Framework servlet, requiring no credentials over HTTP/HTTPS. A crafted POST to /OA_HTML/AppsTCFServer chains SQL injection as the privileged APPS database user into OS command execution under the EBS application account. Horizon3.ai discovered and disclosed this; over 670 internet-exposed EBS instances have been tracked. Patch is available; active scanning is already underway. For enterprises running Oracle E-Business Suite 12.2.3–12.2.15, this is a critical patch-now situation — unpatched instances are effectively advertising open shells to anyone scanning the internet. Defenders should also hunt: review web logs for unauthenticated POST requests to the TCF servlet invoking GanttDataServer, watch for unexpected database activity under the APPS user, and check for the oracle account spawning /bin/sh. The one-day gap between patch and probing underscores that adversaries are monitoring Oracle CPUs as an exploit roadmap.

𝗦𝗸𝘆𝘄𝟰𝗹𝗸𝗲𝗿 𝗗𝗲𝘃𝗶𝗰𝗲 𝗖𝗼𝗱𝗲 𝗣𝗵𝗶𝘀𝗵𝗶𝗻𝗴 𝗖𝗮𝗺𝗽𝗮𝗶𝗴𝗻 𝗧𝗮𝗿𝗴𝗲𝘁𝘀 𝗨𝗦 𝗠𝗮𝗻𝘂𝗳𝗮𝗰𝘁𝘂𝗿𝗶𝗻𝗴, 𝗛𝗲𝗮𝗹𝘁𝗵𝗰𝗮𝗿𝗲, 𝗮𝗻𝗱 𝗧𝗲𝗰𝗵𝗻𝗼𝗹𝗼𝗴𝘆 𝗢𝗿𝗴𝗮𝗻𝗶𝘇𝗮𝘁𝗶𝗼𝗻𝘀 — A threat actor tracked as Skyw4lker is running an active device code phishing campaign against US manufacturing, healthcare, and technology organizations. Victims receive a business-themed lure — a password-protected contract or proposal — that routes them through a Google-hosted redirect page into a legitimate Microsoft authentication flow. Instead of harvesting credentials, attackers abuse the OAuth device authorization grant: they initiate the device code flow on the backend, trick the victim into completing authentication, and collect the resulting Microsoft 365 tokens. No fake login page. No stolen password. A fully legitimate auth event — and a fully compromised account. Security teams face a detection gap that matters: because the authentication event itself is real, traditional credential-theft indicators won't fire. Attackers walk away with valid M365 tokens — access to email, SharePoint, Teams, and any connected SaaS the account can reach — while SIEM and identity logs show a normal sign-in. Defenders need to monitor for device code flow usage outside expected devices and geographic baselines, flag Google Sites redirects in email inspection, and treat any unsolicited authentication request from a document as a phishing vector regardless of whether a password was entered.

𝗖𝗿𝗶𝘁𝗶𝗰𝗮𝗹 𝟭𝟲-𝗬𝗲𝗮𝗿-𝗢𝗹𝗱 𝗨𝗘𝗙𝗜 𝗙𝗹𝗮𝘄 𝗶𝗻 𝗘𝗗𝗞 𝗜𝗜 𝗘𝘅𝗲𝗰𝘂𝘁𝗲𝘀 𝗖𝗼𝗱𝗲 𝗕𝗲𝗳𝗼𝗿𝗲 𝗦𝗲𝗰𝘂𝗿𝗲 𝗕𝗼𝗼𝘁 𝗼𝗻 𝗡𝗲𝘁𝘄𝗼𝗿𝗸-𝗕𝗼𝗼𝘁𝗶𝗻𝗴 𝗦𝗲𝗿𝘃𝗲𝗿𝘀 — CVE-2026-97631, scored 9.5, is a buffer overflow buried in EDK II's PXE driver since a November 2010 commit. An unauthenticated attacker on the same network segment sends a crafted ICMP message during PXE boot, overflows a fixed 504-byte buffer, and executes arbitrary code entirely before Secure Boot can intervene. Downstream firmware from AMI, Insyde, Phoenix, and Microsoft's Project Mu fork are all affected; no stable EDK II release carries the patch yet. For data center and server teams, the exposure calculus is straightforward: any rack or cloud instance that PXE-boots is vulnerable until the firmware vendor ships an update, and no software workaround exists short of disabling PXE outright. The deeper risk flagged by Dragos is that an attacker who hijacks control at this pre-boot stage also has unobstructed access to the TPM — opening a realistic path to attacking disk encryption. Audit your environment now for PXE-dependent servers, pressure firmware vendors for patch timelines, and treat this as a priority for your next maintenance window regardless of the no-known-exploitation status.

𝗔𝗡𝗠 𝗙𝗜𝗔𝗹𝗶𝗵 𝗥𝗔𝗻𝗼𝗺𝗾𝗔𝗿𝗜 𝗔𝘁𝘁𝗜𝗰𝗸 𝗗𝗶𝗼𝗿𝘂𝗽𝘁𝗼 𝗣𝗜𝘁𝗶𝗜𝗻𝘁 𝗖𝗜𝗿𝗜 𝗔𝗻𝗱 𝗦𝘂𝗿𝗟𝗜𝗿𝗶𝗜𝗼 — New Mexico’s only academic medical center and Level 1 trauma center disclosed a ransomware attack that took systems offline, forced cancellation and delays of surgical procedures, and disrupted patient care across the facility. No threat actor has claimed responsibility. Healthcare environments sit at the worst intersection for ransomware: life-critical uptime requirements, fragmented legacy clinical systems, and data that commands premium ransom leverage. A Level 1 trauma center going dark isn’t just an IT incident — it’s a patient safety event. Security teams supporting healthcare should treat network segmentation between clinical and administrative systems as non-negotiable, validate that offline backup restoration has been tested under realistic incident conditions, and ensure IR playbooks specifically address care-continuity scenarios where the standard “take it offline” response isn’t an option.

𝗪𝗵𝗮𝘁 𝗛𝗮𝗽𝗽𝗲𝗻𝘀 𝗪𝗵𝗲𝗻 𝗦𝗲𝗰𝘂𝗿𝗶𝘁𝘆 𝗧𝗼𝗼𝗹𝘀 𝗚𝗼 𝗗𝗮𝗿𝗸 𝗕𝗲𝗳𝗼𝗿𝗲 𝘁𝗵𝗲 𝗥𝗮𝗻𝘀𝗼𝗺𝘄𝗮𝗿𝗲 — Storm-2603 𝗗𝗶𝘀𝗮𝗯𝗹𝗲𝘀 𝟰𝟬 𝗛𝗼𝘀𝘁𝘀 𝗶𝗻 𝟮 𝗛𝗼𝘂𝗿𝘀: China-linked Storm-2603 (Warlock ransomware) breached at least four organizations — a water utility, telecom, regional government, and university — via on-premises SharePoint vulnerabilities. After nine days of quiet reconnaissance, attackers rolled out a security-tool killer across 40 hosts in roughly two hours, then leveraged SYSVOL replication to push Warlock to 33 endpoints. Encryption followed almost immediately once defenses were gone. The playbook here is a direct challenge to detection-dependent security architectures. Nine days of dwell time means EDR and SIEM had every opportunity to surface the intrusion — and didn't, or weren't actioned in time. The kill-the-watcher-first move means that by the time ransomware ran, the hosts were effectively blind. Security teams should pressure-test whether their endpoint controls can survive an active tamper attempt, audit privileged account creation against SharePoint service account naming patterns, and verify that SYSVOL integrity monitoring is in place — because the delivery mechanism here was the domain's own replication infrastructure.

𝗔𝗯𝗹𝗵𝗿𝗼𝗽𝗶𝗰’𝘀 𝗨𝗯𝗿𝗲𝗹𝗲𝗮𝘀𝗲𝗱 𝗔𝗜 𝗠𝗼𝗱𝗲𝗹 𝗖𝗵𝗮𝗶𝗯𝘀 𝗙𝗹𝗮𝘇𝘀 𝗜𝗯𝗹𝗼 𝗪𝗼𝗿𝗴𝗶𝗯𝗴 𝗖𝗵𝗿𝗼𝗠𝗲, 𝗦𝗮𝗳𝗮𝗿𝗶, 𝗪𝗶𝗯𝗱𝗼𝘇𝘀 𝗮𝗯𝗱 𝗟𝗶𝗯𝘂𝗱 𝗘𝗱𝗽𝗹𝗼𝗶𝗹𝘀 — Anthropic’s Frontier Red Team deployed an internal, unreleased AI model to autonomously discover and chain multiple vulnerabilities into five working exploits targeting Chrome, Safari, Windows, Linux, and Android — requiring minimal human involvement. The Linux chain achieved unauthenticated remote root in under an hour via a kernel KASLR bypass and race condition. Chrome exploits included 13 sandbox escapes across 62 reported critical and high-severity flaws. All vulnerabilities were disclosed to vendors under coordinated disclosure and patched before publication. This is a structural shift in the threat landscape that every security team needs to absorb now. AI has crossed the threshold from finding individual bugs to autonomously chaining multi-flaw exploit sequences — the kind of work that previously required elite, specialized red teams with deep platform knowledge. That capability compression means the window between vulnerability disclosure and weaponized exploit narrows dramatically for any adversary with access to capable AI tooling. For CISOs, this demands a hard look at patch SLAs for critical and high-severity CVEs in browser fleets, kernel stacks, and network-facing services — because the bar for building working exploit chains just got significantly lower. Memory-safety investments, exploit surface reduction, and runtime protection layers (like Morphisec’s moving target defense) become more urgent when AI can automate the hardest parts of the attack chain.

𝗧𝗼𝗱𝗮𝘆'𝘀 𝗧𝗵𝗿𝗲𝗮𝘁 𝗜𝗻𝘁𝗲𝗹 𝗦𝘂𝗺𝗺𝗮𝗿𝘆 AI now chains zero-days autonomously across Chrome, Safari, Windows & Linux — the expert bottleneck is gone. China's Warlock ransomware silenced 40 hosts in 2 hrs. A 16-yr UEFI flaw survives every OS wipe and reinstall.

𝗶𝗿𝗮𝗰𝗹𝗲 𝗘-𝗕𝗨𝗴𝗶𝗲𝗴𝗴 𝗦𝘀𝗜𝗲𝗴 𝗖𝗩𝗘-𝟯𝟬𝟮𝟬-𝟱𝟬𝟱𝟯𝟬𝟯 (𝗖𝗩𝗦𝗦 𝟯.𝟮): 𝗔𝗰𝗳𝗶𝗳𝗲 𝗦𝗰𝗮𝗻𝗻𝗶𝗻𝗴 𝗕𝗲𝗴𝗶𝗻𝗴 𝗗𝗮𝘆 𝗔𝗳𝗳𝗲𝗿 𝗶𝗿𝗮𝗰𝗹𝗲 𝗣𝗮𝗳𝗰𝗵𝗲𝗴 𝗦𝗤𝗟 𝗜𝗻𝗷𝗲𝗰𝗳𝗶𝗳𝗻 𝗥𝗖𝗘 𝗖𝗵𝗮𝗶𝗻. Defused Cyber honeypots logged live exploitation attempts within 24 hours of Oracle’s Critical Patch Update dropping. The vulnerability — an unauthenticated SQL injection in the Thin Client Framework servlet — chains directly to remote code execution, no credentials required. Horizon3.ai discovered it; attackers were scanning for it the next morning. Oracle EBS sits at the core of enterprise financial, HR, and supply chain operations — exactly the foothold ransomware operators want. The real exposure isn’t just the CVSS score: EBS patch cycles routinely lag weeks or months because production validation is slow and complex, leaving most organizations unpatched while active scanning is already underway. Adaptive moving target defense blocks the RCE payload at the memory level regardless of patch status — injected shellcode cannot resolve the runtime addresses it targets because AMTD’s continuous randomization has already shifted them. For security teams that cannot wait on Oracle’s patch validation cycle, in-memory protection closes the window that patching cannot. (ATT&CK: T1190, T1203)

𝗦𝗸𝗬𝗪𝟰𝗅𝗸𝗲𝗲𝗿 𝗗𝗲𝗳𝗶𝗰𝗲 𝗖𝗸𝗱𝗲 𝗣𝗵𝗶𝗳𝗵𝗶𝗻𝗴 𝗖𝗮𝗺𝗽𝗮𝗶𝗴𝗻 𝗧𝗮𝗿𝗴𝗲𝗳𝗰 𝗨𝗦 𝗠𝗮𝗻𝗸𝗳𝗮𝗰𝗳𝗸𝗿𝗶𝗻𝗴, 𝗛𝗲𝗮𝗹𝗳𝗵𝗰𝗮𝗿𝗲, 𝗮𝗻𝗱 𝗧𝗲𝗰𝗵𝗻𝗸𝗹𝗸𝗴𝗬 𝗢𝗿𝗴𝗮𝗻𝗶𝗯𝗮𝗳𝗶𝗸𝗻𝗰 — The Skyw4lker campaign is abusing Microsoft’s legitimate OAuth device code authentication flow to silently hijack M365 and Entra ID sessions across U.S. manufacturing, healthcare, and technology sectors. Victims enter a real code on a real Microsoft sign-in page, complete MFA as expected — and the attacker walks away with a fully authenticated session. No stolen passwords. No failed MFA prompts. No alerts. Google-hosted infrastructure and business-themed lures keep suspicion low. This is an identity-layer attack that operates entirely within the bounds of your existing security investment. Your email gateway doesn’t flag it. Your MFA isn’t bypassed — it’s completed. The Microsoft sign-in page is genuine. Enterprise security teams that have built their identity posture around Entra ID and MFA need to recognize that session hijacking via device code flow is a blind spot those controls were never designed to address. Once an attacker holds a valid M365 session, the pivot to SharePoint and OneDrive for payload staging is straightforward — turning trusted collaboration infrastructure into a delivery mechanism. Detecting unauthorized OAuth grants and anomalous app registrations created post-compromise is where monitoring needs to focus. (ATT&CK: T1528, T1078.004, T1566.003)

𝗖𝗿𝗶𝘁𝗶𝗰𝗮𝗹 𝟭𝟲-𝗬𝗲𝗮𝗿-𝗢𝗹𝗱 𝗨𝗘𝗙𝗜 𝗙𝗹𝗮𝘄 𝗶𝗻 𝗘𝗗𝗞 𝗜𝗜 𝗘𝘅𝗲𝗰𝘂𝘁𝗲𝘀 𝗖𝗼𝗱𝗲 𝗕𝗲𝗳𝗼𝗿𝗲 𝗦𝗲𝗰𝘂𝗿𝗲 𝗕𝗼𝗼𝘁 𝗼𝗻 𝗡𝗲𝘁𝘄𝗼𝗿𝗸-𝗕𝗼𝗼𝘁𝗶𝗻𝗴 𝗦𝗲𝗿𝘃𝗲𝗿𝘀 — CVE-2026-97631 is a critical flaw in EDK II, the open-source UEFI firmware base used by virtually every major hardware vendor. An unauthenticated attacker on the same network segment can deliver a crafted packet during the PXE boot window to execute arbitrary code before Secure Boot loads — before any OS security control has initialized. The vulnerability dates to roughly 2010. A patch is available from TianoCore, but vendor-specific firmware updates will take months to reach enterprise fleets. This is a firmware persistence story, not an active exploit-in-the-wild alert — and that distinction matters more than it might appear. Enterprise server firmware update cycles routinely run 6 to 18 months, meaning the window between patch availability and actual deployment is wide. An attacker who exploits this before a firmware update lands gains pre-OS persistence that survives disk wipes, OS reinstalls, and endpoint agent resets. Security teams should treat this as a forcing function to audit firmware update cadence across server infrastructure, inventory PXE-booting systems, and evaluate network segmentation controls that limit adjacent-network attacker access during boot sequences. UEFI-level implants operate below most runtime detection layers, so the honest posture is: reduce exposure now through network controls, accelerate firmware patching timelines, and plan for the reality that "we'll patch it eventually" is not an adequate response at the firmware layer.

𝗨𝗡𝗠 𝗛𝗲𝗮𝗹𝘁𝗵 𝗥𝗮𝗻𝘀𝗼𝗺𝘄𝗮𝗿𝗲 𝗔𝘁𝘁𝗮𝗰𝗸 𝗗𝗶𝘀𝗿𝘂𝗽𝘁𝘀 𝗣𝗮𝘁𝗶𝗲𝗻𝘁 𝗖𝗮𝗿𝗲 𝗮𝗻𝗱 𝗦𝘂𝗿𝗴𝗲𝗿𝗶𝗲𝘀 — The University of New Mexico Health Sciences Center — the state's only academic medical center and Level 1 trauma center — disclosed a ransomware attack that caused system outages, disrupted patient care, and forced cancellations and delays of surgical procedures. No group has claimed responsibility; the investigation is ongoing. Healthcare is the sector where ransomware stops being an IT problem and becomes a patient safety problem. A Level 1 trauma center losing systems doesn't mean productivity loss — it means the highest-acuity patients in the state face delayed or cancelled procedures. Clinical environments compound the challenge: Windows workstations live alongside medical devices with strict software compatibility requirements, limiting the security controls teams can deploy without risking device interference. Yet those same endpoints remain primary ransomware targets (ATT&CK: T1486, T1490). For enterprise security leaders in health systems, this is a reminder that the recovery calculus is different — downtime isn't measured in SLA penalties, it's measured in patient outcomes. The question isn't whether ransomware will reach clinical endpoints, but whether your controls can stop encryption before the ransom demand arrives.

𝗪𝗵𝗮𝘁 𝗛𝗮𝗽𝗽𝗲𝗻𝘀 𝗪𝗵𝗲𝗻 𝗦𝗲𝗰𝘂𝗿𝗶𝘁𝘆 𝗧𝗼𝗼𝗹𝘀 𝗚𝗼 𝗗𝗮𝗿𝗸 𝗕𝗲𝗳𝗼𝗿𝗲 𝘁𝗵𝗲 𝗥𝗮𝗻𝘀𝗼𝗺𝘄𝗮𝗿𝗲 — 𝗦𝘁𝗼𝗿𝗺-𝟮𝟲𝟬𝟯 (𝗪𝗮𝗿𝗹𝗼𝗰𝗸) 𝗗𝗶𝘀𝗮𝗯𝗹𝗲𝘀 𝟰𝟬 𝗛𝗼𝘀𝘁𝘀 𝗶𝗻 𝟮 𝗛𝗼𝘂𝗿𝘀 — China-linked Storm-2603 entered through an unpatched SharePoint server, spent nine days quietly building persistence, then executed a two-phase strike: a custom tool stripped endpoint protection from at least 40 machines in roughly 120 minutes — one host going dark every three minutes — before Warlock ransomware was staged in SYSVOL and replicated automatically across the domain. Targeted organizations included a water utility, a telecom provider, a regional government, and a university, all in Portuguese- and Spanish-speaking countries across Europe, Africa, and Latin America. The operational lesson here is sequencing: the attacker's primary objective was not the data — it was the detection layer. The ransomware deployment was almost perfunctory once protection was gone, taking less than two hours to go domain-wide. This should prompt every security team to stress-test a specific failure mode: if an adversary who has been present for nine days runs a single script and your EDR goes silent on 40 endpoints simultaneously, what visibility and response capability remains? Organizations that have consolidated their entire detection posture into user-mode endpoint agents are exposed to exactly this class of pre-ransomware sabotage. Resilient architectures maintain detection mechanisms that are isolated from the same privilege tier an attacker can reach — and they have practiced response playbooks for the scenario where the primary tool is the first casualty.

𝗔𝗻𝘁𝗵𝗿𝗼𝗽𝗶𝗰’𝘀 𝗨𝗻𝗿𝗲𝗹𝗲𝗮𝘀𝗲𝗱 𝗔𝗜 𝗠𝗼𝗱𝗲𝗹 𝗖𝗵𝗮𝗶𝗻𝘀 𝗙𝗹𝗮𝘄𝘀 𝗜𝗻𝘁𝗼 𝗪𝗼𝗿𝗸𝗶𝗻𝗴 𝗖𝗵𝗿𝗼𝗺𝗲, 𝗦𝗮𝗳𝗮𝗿𝗶, 𝗪𝗶𝗻𝗱𝗼𝘄𝘀 𝗮𝗻𝗱 𝗟𝗶𝗻𝘂𝘅 𝗘𝘅𝗽𝗹𝗼𝗶𝘁𝘀 — An unreleased Anthropic model autonomously discovered vulnerabilities across Chrome, Safari, Android, Windows, and Linux, then chained multiple flaws into working proof-of-concept exploits. One PoC executed on a stock Mac within seconds of a page load. Anthropic responsibly disclosed every bug before publishing — all are now patched — but the capability itself is the headline: what previously required a specialist red team over weeks now takes one model and a prompt. The expert bottleneck that gave defenders time to patch is gone. This is not an isolated data point — OpenAI demonstrated a $250K Chrome full-chain last month, and Google Project Zero’s AI-vs-fuzzer benchmarks make the trend empirical: two frontier labs have now proven autonomous multi-platform exploit chaining at scale. For enterprise security teams, the direct implication is that AI-generated exploits can be unique per target, meaning signature databases and behavioral detection models trained on human-authored attack patterns will systematically lag. The development timeline advantage defenders depended on — weeks of attacker effort — has collapsed to hours. Treat autonomous exploit generation as an active adversarial capability today, not a future planning assumption, and prioritize runtime attack surface reduction strategies that remain effective regardless of how or how fast an exploit was built.

𝟵𝟱𝟯 𝗠𝗮𝗴𝗲𝗻𝘁𝗼 𝗦𝘁𝗼𝗿𝗲𝘀 𝗜𝗻𝗳𝗲𝗰𝘁𝗲𝗱: 𝗝𝗮𝘃𝗮𝗦𝗰𝗿𝗶𝗽𝘁 𝗦𝗸𝗶𝗺𝗺𝗲𝗿 𝗦𝗲𝗿𝘃𝗲𝘀 𝗣𝗮𝘆𝗹𝗼𝗮𝗱 𝗢𝗻𝗹𝘆 𝘁𝗼 𝗥𝗲𝗮𝗹 𝗦𝗵𝗼𝗽𝗽𝗲𝗿𝘀 — 𝗦𝗰𝗮𝗻𝗻𝗲𝗿𝘀 𝗚𝗲𝘁 𝗡𝗼𝘁𝗵𝗶𝗻𝗴. Dutch e-commerce security firm Sansec has documented a skimming campaign running since July 2025 that has compromised 953 Magento-based online stores. The injected JavaScript fingerprints incoming requests and delivers its card-harvesting payload only to genuine human shoppers — automated crawlers and security scanners receive clean, unmodified code and see nothing wrong. This is a direct challenge to any compliance or third-party audit program that relies on automated storefront scanning. A Magento deployment can pass a routine security scan and simultaneously be exfiltrating live payment card data. Security and risk teams overseeing e-commerce infrastructure need to treat real-browser behavioral monitoring and runtime JavaScript integrity checks as mandatory controls — not optional supplements to static analysis. Stores that have not audited Magento extension integrity since mid-2025 should treat themselves as potentially compromised until proven otherwise.

𝗔𝘂𝘀𝘁𝗿𝗮𝗹𝗶𝗮’𝘀 𝗔𝗦𝗗 𝗦𝗲𝗶𝘇𝗲𝘀 𝗔𝗺𝗮𝗱𝗲𝘆 𝗕𝗼𝘁𝗻𝗲𝘁 𝗕𝗮𝗰𝗸𝗲𝗻𝗱 — 𝟭𝟴𝟬,𝟬𝟬𝟬 𝗜𝗻𝗳𝗲𝗰𝘁𝗲𝗱 𝗘𝗻𝗱𝗽𝗼𝗶𝗻𝘁𝘀 𝗗𝗶𝘀𝗰𝗼𝗻𝗻𝗲𝗰𝘁𝗲𝗱 𝗚𝗹𝗼𝗯𝗮𝗹𝗹𝘆. Australia's ASD sinkholed the command-and-control infrastructure behind Amadey, a commodity malware loader that had been staging ransomware and infostealer payloads across 180,000 compromised endpoints worldwide. The operation cuts the C2 lifeline — but the infected hosts remain, and Amadey's operators can rebuild infrastructure faster than defenders can re-image fleets. The sinkhole buys time, not resolution. If Amadey touched your environment, the loader already dropped secondary payloads before this takedown. Hunt for Amadey's known staging directories, scheduled task persistence, and any credential-harvesting tools it commonly delivers — RedLine, Vidar, LockBit precursors. Treat every endpoint that beaconed to now-seized C2 infrastructure as fully compromised, not merely quarantined. Law enforcement actions on commodity botnets are temporary disruptions; the underlying infection problem on your endpoints is yours to solve.

𝗠𝗶𝗰𝗿𝗼𝘀𝗼𝗳𝘁 𝗔𝘂𝘁𝗵𝗲𝗻𝘁𝗶𝗰𝗮𝘁𝗼𝗿 𝗖𝗩𝗘-𝟮𝟬𝟮𝟲-𝟴𝟬𝟬𝟵𝟳: 𝗣𝗲𝗿𝗺𝗶𝘀𝘀𝗶𝗼𝗻𝗹𝗲𝘀𝘀 𝗔𝗻𝗱𝗿𝗼𝗶𝗱 𝗔𝗽𝗽 𝗦𝗶𝗹𝗲𝗻𝘁𝗹𝘆 𝗦𝘁𝗲𝗮𝗹𝘀 𝗘𝗻𝘁𝗲𝗿𝗽𝗿𝗶𝘀𝗲 𝗪𝗼𝗿𝗸 𝗔𝗰𝗰𝗼𝘂𝗻𝘁 𝗧𝗼𝗸𝗲𝗻𝘀 — A now-patched flaw in Microsoft Authenticator for Android allowed any installed app — no special permissions required — to impersonate Microsoft’s own apps and silently collect enterprise OAuth tokens, delivering full access to email, files, and calendar data without the user ever seeing a prompt or alert. Any Android device in your fleet that ran an unpatched Authenticator version was a silent credential tap for every M365 work account bound to it. If your MDM policy doesn’t enforce Authenticator version minimums, your exposure window is unknown — cross-reference against anomalous M365 sign-in events from the past several months and treat unverified devices as potentially compromised. The authenticator itself became the attack surface; that’s a trust-chain failure worth reviewing in your mobile security posture.

𝗙𝗼𝗿𝗺𝗲𝗿 𝗣𝗲𝗻𝘁𝗲𝘀𝘁𝗲𝗿 𝗨𝘀𝗲𝗱 𝗔𝗥𝗧𝗘𝗫 𝗔𝗜 𝘁𝗼 𝗕𝗿𝗲𝗮𝗰𝗵 𝟵𝟬 𝗢𝗿𝗴𝗮𝗻𝗶𝘇𝗮𝘁𝗶𝗼𝗻𝘀 — 𝟴.𝟮 𝗠𝗶𝗹𝗹𝗶𝗼𝗻 𝗥𝗲𝗰𝗼𝗿𝗱𝘀 𝗦𝘁𝗼𝗹𝗲𝗻, 𝟯𝟴 𝗘𝘅𝘁𝗼𝗿𝘁𝗶𝗼𝗻 𝗗𝗲𝗺𝗮𝗻𝗱𝘀 𝗦𝗲𝗻𝘁. A solo Korean attacker — a former pentester — weaponized the open-source ARTEX AI framework to systematically compromise 90 organizations, exfiltrate 8.2 million records, and send extortion demands to 38 victims, all without the backing of a nation-state or criminal syndicate. This is the same ARTEX AI framework China-linked Storm-0940 used to automate credential attacks at 2,900 sign-in attempts per minute. A lone insider with domain knowledge replicated that operational scale independently. That is the inflection point: AI-assisted attack automation is no longer a differentiator for advanced persistent threats — it is now available to any motivated individual with red team experience. Enterprise security programs need to reassess whether their detection logic is calibrated for attacks that move at machine speed across dozens of targets simultaneously, and whether insider knowledge of offensive tooling in their own red team programs creates an asymmetric residual risk if that expertise walks out the door.

𝗦𝘁𝗼𝗿𝗺-𝟬𝟵𝟰𝟬 (𝗖𝗵𝗶𝗻𝗮) 𝗨𝘀𝗲𝗱 𝗔𝗥𝗧𝗘𝗫 𝗔𝗴𝗲𝗻𝘁𝗶𝗰 𝗔𝗜 𝘁𝗼 𝗪𝗲𝗮𝗽𝗼𝗻𝗶𝘇𝗲 𝗖𝗼𝗻𝗻𝗲𝗰𝘁𝗪𝗶𝘀𝗲 𝗦𝘂𝗽𝗽𝗹𝘆 𝗖𝗵𝗮𝗶𝗻 𝗔𝘁𝘁𝗮𝗰𝗸 — 𝟮,𝟵𝟬𝟬 𝗦𝗶𝗴𝗻-𝗜𝗻 𝗙𝗮𝗶𝗹𝘂𝗿𝗲𝘀 𝗣𝗲𝗿 𝗠𝗶𝗻𝘁𝘂𝘁𝗲. China-nexus threat actor Storm-0940 deployed the ARTEX agentic AI framework to automate a ConnectWise supply chain attack at machine scale — 2,900 credential stuffing attempts per minute, a velocity no human operator can replicate. The same open-source ARTEX tooling was separately used by a solo Korean pentester to compromise 90 organizations, confirming the framework has crossed from nation-state exclusive into broadly accessible threat infrastructure. If ConnectWise is anywhere in your remote management or MSP stack, this changes your risk calculus immediately. Agentic AI collapses the timeline between initial access and lateral movement — detection windows that assumed human-paced attacks are now dangerously wide. Alert thresholds tuned for normal authentication noise will not surface 2,900 failures per minute as an anomaly without deliberate recalibration. Security teams should audit ConnectWise integrations, enforce MFA without exception on all remote management tooling, and pressure-test whether their SIEM and EDR rules were built for a world where a single threat actor can sustain nation-state-grade automation with an open-source AI agent.

𝗧𝗼𝗱𝗮𝘆'𝘀 𝗧𝗵𝗿𝗲𝗮𝘁 𝗜𝗻𝘁𝗲𝗹 𝗦𝘂𝗺𝗺𝗮𝗿𝘆 ARTEX AI is fueling attacks from nation-states to solo hackers; Microsoft Authenticator silently leaked enterprise tokens via CVE-2026-80097; Australia sinkholed Amadey's C2 across 180K endpoints — but the loader lives on.

𝟵𝟱𝟯 𝗠𝗮𝗴𝗲𝗻𝘁𝗼 𝗦𝘁𝗼𝗿𝗲𝘀 𝗜𝗻𝗳𝗲𝗰𝘁𝗲𝗱: 𝗝𝗮𝘃𝗮𝗦𝗰𝗿𝗶𝗽𝘁 𝗦𝗸𝗶𝗺𝗺𝗲𝗿 𝗦𝗲𝗿𝘃𝗲𝘀 𝗣𝗮𝘆𝗹𝗼𝗮𝗱 𝗢𝗻𝗹𝘆 𝘁𝗼 𝗥𝗲𝗮𝗹 𝗦𝗵𝗼𝗽𝗽𝗲𝗿𝘀 — 𝗦𝗰𝗮𝗻𝗻𝗲𝗿𝘀 𝗚𝗲𝘁 𝗡𝗼𝘁𝗵𝗶𝗻𝗴. Sansec documented a campaign running since July 2025 that compromised 953 Magento storefronts by planting a malicious JavaScript loader inside CMS database blocks. The attacker's server fingerprints every inbound request — security scanners receive a blank response while real shoppers get a skimmer that persists across sessions via localStorage, with a second variant adding browser fingerprinting for additional scanner filtering. Five rotating C2 domains have kept the operation alive for over 15 months. The evasion logic here is the same philosophy that drives fileless and in-memory malware: detonate only against real targets, present nothing to inspection tooling. Traditional web application scanners are defeated by design — the server decides what code reaches the browser, and if that decision is conditional on who's asking, scan-based detection is blind. For enterprises running retail, hospitality, or e-commerce properties, this campaign marks a concrete inflection point: once the web application layer is compromised, endpoint-side exfil prevention operating inside the browser process itself is the last enforceable control standing between an attacker's skimmer and customer payment data on managed endpoints.