the threat gazette
Morning Edition
Supply Chain

marimo Pre-Auth RCE Weaponized in 72 Hours; NKAbuse Botnet Staged on HuggingFace Spaces

CVE-2017-5638 CVE-2026-39987 NKAbuse Net Crawler Royal

CVE-2026-39987, a critical pre-authentication RCE in the marimo reactive Python notebook platform, was weaponized within three days of its April 8 disclosure, with Sysdig TRT confirming multiple attacks by April 11 and capturing a previously undocumented NKAbuse variant staged on HuggingFace Spaces. The actor exploited HuggingFace's high developer trust and frequent allow-listing as a malware CDN — a tactically sound choice for reaching data science workloads. NKAbuse's use of the NKN blockchain protocol for C2 structurally resists traditional infrastructure takedown and sinkholing, giving this botnet a meaningful operational longevity advantage over conventional C2 architectures. The entry also tags CVE-2017-5638 (Apache Struts, EPSS 0.943, in KEV since 2022), and the appearance of 'Royal' in the software entities warrants monitoring for a potential ransomware-as-second-stage pivot.

The 72-hour disclosure-to-weaponization window against developer tooling, combined with HuggingFace staging and blockchain C2, describes an actor running a pre-positioned rapid exploitation playbook — not an opportunistic scanner. The HuggingFace angle specifically should prompt a review of whether your threat intel and endpoint controls treat downloads from model hosting platforms with the same scrutiny as generic CDNs, because they frequently don't.

Three-day disclosure-to-weaponization plus HuggingFace as malware CDN plus NKN blockchain C2 is a pre-positioned playbook, not opportunistic scanning — and data-science workloads are exactly the kind of high-privilege, loosely-governed endpoints that benefit from trusting model-hosting infra by default. The Royal tag in extracted software warrants watching for a ransomware second stage; NKN-based C2 is also a longevity pattern other crews will copy once this writeup circulates.

2026-04-09
2 sources
+ CVE-2026-39987
2026-04-10
1 source
2026-04-12
1 source
2026-04-13
1 source
2026-04-15
1 source
+ CVE-2017-5638
2026-04-16
1 source

Editorial

The blockchain C2 thread flagged yesterday just cashed out in concrete form. The Marimo exploitation chain — now a week old and still generating entries — terminates in Sysdig's discovery of an undocumented NKAbuse variant staged on HuggingFace Spaces and beaconing over NKN. That's the UNC5142/UNC5342 tradecraft pattern proliferating into opportunistic commodity operations faster than expected, and it pairs with the malicious LLM proxy router finding to form a coherent message: AI/ML platforms are being treated as generic CDNs by allow-list policy, but they now host both C2 staging and hostile egress infrastructure. If the enterprise AI rollout delegated proxy configuration to application teams without central network visibility, that's the control gap being monetized today.

The counter-signal is a 17-year-old Excel bug (CVE-2009-0238) landing in KEV with confirmed exploitation on the same cycle that shipped an already-exploited SharePoint flaw (CVE-2026-32201). One cohort is building blockchain-resilient C2; another is exhuming bugs older than the analysts triaging them — and both are working. Add Sandworm teaming with NoName057 against a Swedish thermal plant, and the week's connective tissue is clear: the attack surface is widening at both temporal extremes and across the state/criminal/hacktivist boundary simultaneously. Vulnerability management scoring that implicitly privileges "recent" is mis-calibrated for this threat environment, and the Rapid7 pre-KEV triage list of 19 Microsoft "more likely to be exploited" CVEs is the right artifact to cross-reference against internet-exposed and privileged-access assets before next week's additions prove the point.

Notable

Vulnerabilities

CVE-2009-0238: Seventeen-Year-Old Excel Flaw Enters KEV With Active Exploitation

CVE-2009-0238 CVE-2026-32201 CVE-2026-33824 CVE-2026-33825

CISA added CVE-2009-0238, an Excel vulnerability first published in February 2009 with CVSS 9.3 and a current EPSS of 0.572, to the KEV catalog with a remediation deadline of 2026-04-28, confirming active attacks against the 17-year-old flaw. The elevated EPSS is algorithmically significant — it reflects recent exploitation telemetry biasing the model, meaning attacker interest is measurably elevated now rather than being a stale residual score. CVE-2026-32201, a SharePoint Server input validation flaw allowing pre-authentication network spoofing, is also confirmed exploited in the wild and carries the same KEV deadline of 2026-04-28. No attribution has been published for either exploitation chain.

The Excel CVE revival is most concerning for environments where Office patch cycles have been deferred due to macro compatibility concerns or legacy line-of-business application dependencies — a pattern disproportionately common in financial services operations. The absence of attribution here is itself notable; a 17-year-old CVE with a 0.572 EPSS and no named actor suggests either a novel exploitation path rediscovery or a deliberate choice to weaponize a bug that many defenders have mentally retired.

EPSS at 0.572 on a 2009 CVE is a telemetry artifact of *current* attacker interest, not a stale residual — the model is telling you someone is actively using this right now. Pairs cleanly with the SharePoint zero-day (CVE-2026-32201) from yesterday's Patch Tuesday; environments where Office patching was deferred for macro or LOB compatibility are the target profile.

Vulnerabilities

Rapid7: Microsoft Self-Flags 19 April CVEs as 'More Likely' To Be Exploited

CVE-2026-32201 CVE-2026-33824 CVE-2026-33825

Rapid7's April 2026 Patch Tuesday analysis confirms 167 Microsoft CVEs — including 80 browser CVEs counted separately — with Microsoft's own exploitation likelihood assessments designating 19 as 'more likely to see future exploitation.' CVE-2026-32201 (SharePoint, KEV 2026-04-28) is the sole confirmed-exploited entry at publication time, with CVE-2026-33824 and CVE-2026-33825 also tracked in Rapid7's coverage. The 19-CVE exploitation-likely list represents Microsoft's internal threat intelligence team's forward-looking assessment, making it a pre-KEV indicator of near-term weaponization candidates.

Microsoft's 'exploitation more likely' designations on 19 CVEs in this batch are an underutilized triage input — they represent the judgment of Microsoft's own detection engineering and threat intel teams, not a CVSS formula. In a 167-CVE cycle, cross-referencing that specific list against your internet-exposed and privileged-access asset inventory is the most efficient path to a second-tier remediation queue beyond the KEV entries.

Microsoft's internal exploitation-likelihood designation is the most underused triage input in the ecosystem — it's the judgment of MSRC's own detection-engineering and threat intel teams, not a CVSS formula. In a 167-CVE cycle, that 19-CVE list is the efficient second-tier queue once the KEV entries are handled.

Malware

Malicious LLM Proxy Routers in the Wild; Scattered Spider Among Cited Actors

CVE-2025-0520 CVE-2026-32201 CVE-2026-5194 APT3 APT37 Scattered Spider Milan UPPERCUT

Risky Biz News reports on malicious LLM proxy router infrastructure deployed in the wild, with activity attributed across APT3 (China), APT37 (North Korea), and Scattered Spider (UNC3944, financially motivated) — actors with entirely different sponsor contexts and operational models, almost certainly representing distinct campaign items within the newsletter's roundup format rather than a coordinated joint operation. Tooling includes Milan and UPPERCUT; UPPERCUT has historical APT10/MenuPass associations rather than APT3, flagging a potential attribution precision issue or evidence of cross-group tool sharing in the source reporting. The malicious proxy technique involves adversary-controlled LLM API infrastructure positioned to intercept, exfiltrate, or manipulate enterprise AI traffic. CVE-2026-5194 (EPSS 0.00035) and CVE-2025-0520 (EPSS 0.020) are also tagged but carry minimal exploitation signal.

The three-actor framing should not be read as a coordinated joint operation — it isn't. What is independently significant is Scattered Spider's apparent pivot toward AI infrastructure targeting: this group's demonstrated track record against financial services firms via social engineering, combined with LLM proxy interception techniques, describes a threat model directly relevant to institutions running internal LLM services or routing to third-party AI APIs through enterprise gateways. Verify that your AI API traffic paths are not traversing adversary-controlled infrastructure, particularly in environments where LLM proxy configuration has been delegated to application teams without central network visibility.

The three-actor framing (APT3, APT37, Scattered Spider) is almost certainly a newsletter-roundup artifact rather than a joint op — and the UPPERCUT/APT3 pairing specifically looks like an attribution slip (UPPERCUT is APT10/MenuPass tooling). What matters for us is Scattered Spider pivoting toward AI infrastructure: a group with a demonstrated financial-services track record via social engineering now moving against LLM traffic paths is a direct threat-model update.

Privacy

Salt Typhoon Operational Security and Critical Infrastructure Targeting: Deep-Dive

Salt Typhoon Attor CALENDAR Qilin

Long-form technical analysis of Salt Typhoon's tradecraft, targeting selection, and OPSEC across critical infrastructure intrusions — strategic context rather than a fresh incident, but substantive enough (2,900+ words) to use as a reference piece for threat modeling telecom and infrastructure dependencies.

Geopolitical

Sandworm and NoName057 Combined Attempt Against Swedish Thermal Power Plant

NoName057 Sandworm Team

Swedish critical infrastructure targeted in a blended operation combining GRU-linked Sandworm capability with the pro-Russian NoName057 hacktivist front. The state-plus-hacktivist pairing against ICS is a tradecraft pattern worth logging — plausible cover-and-access division of labor rather than noise.

Intelligence

Novel BGP Manipulation Vector in IXP Route Server Architecture

Researcher disclosure of a previously undocumented blind spot in Internet Exchange Point route server configurations enabling BGP manipulation. Relevant to any institution with BGP-adjacent dependencies (transit, anycast DNS, DDoS scrubbing) — worth a conversation with network engineering on upstream IXP exposure.

AI Threats

n8n Workflow Automation Abused for Reconnaissance and Attack Staging

Threat actors operationalizing the legitimate n8n automation platform as recon and credential-harvesting infrastructure. Continues the pattern of living-off-trusted-SaaS (GitHub Actions, HuggingFace, now n8n) — allow-listing by vendor reputation continues to age poorly as an EDR/proxy posture.

Briefs

Vulnerabilities

Talos Snort Rule Coverage for April 2026 Patch Tuesday (165 Microsoft CVEs)

Microsoft released 32 security patches including one CISA Known Exploited Vulnerability with due date 2026-04-28, spanning critical infrastructure-relevant products.

CVE-2026-0390 CVE-2026-23666 CVE-2026-26151 CVE-2026-26169 CVE-2026-26173 CVE-2026-26177 CVE-2026-26182 CVE-2026-27906 CVE-2026-27908 CVE-2026-27909 CVE-2026-27913 CVE-2026-27914 CVE-2026-27921 CVE-2026-27922 CVE-2026-32070 CVE-2026-32075 CVE-2026-32093 CVE-2026-32152 CVE-2026-32154 CVE-2026-32155 CVE-2026-32157 CVE-2026-32162 CVE-2026-32190 CVE-2026-32201 CVE-2026-32202 CVE-2026-32225 CVE-2026-33114 CVE-2026-33115 CVE-2026-33824 CVE-2026-33825 CVE-2026-33826 CVE-2026-33827