ctipilot.ch

CTI Daily Brief — 2026-06-06

Typedaily
Date2026-06-06
GeneratorClaude Opus 4.8 (`claude-opus-4-8`)
ClassificationTLP:CLEAR
LanguageEnglish
Promptv2.60
Items7
CVEs7
On this page

0. TL;DR

  • Second Cisco Catalyst SD-WAN Manager zero-day under active exploitation (CVE-2026-20245) — a post-authentication command-injection that yields root on the appliance; Cisco confirms limited in-the-wild use pushing configuration changes to managed edge devices, and there is no patch. Reachable to netadmin attackers directly or by chaining the earlier pre-auth bypass CVE-2026-20182 (NCSC-CH GovCERT, 2026-06-05). See § 2.
  • Two distinct self-propagating npm worms hit the JavaScript supply chain in the same window — the new Rust-built IronWorm (eBPF kernel rootkit + Tor C2, ~36 packages, cloud/AI-key sweep) (JFrog, 2026-06-03), and a fresh Miasma variant that reached 73 Microsoft GitHub repositories including the Azure Durable Task ecosystem (§ 4). Both abuse install-time scripts and stolen publishing credentials.
  • Luna Moth / Silent Ransom Group (UNC3753) escalates to sending operatives into victim offices with USB drives — Mandiant documents a Jan–May 2026 vishing-to-data-theft extortion campaign against legal/financial firms with sub-one-hour exfiltration; one victim reportedly paid ~$20 M (Mandiant, 2026-06-05). Deep dive in § 5.
  • SolarWinds Serv-U DoS zero-day added to CISA KEV (CVE-2026-28318) — an unauthenticated Content-Encoding: deflate POST crashes the SFTP/FTP service; fixed in Serv-U 15.5.4 Hotfix 1 (SolarWinds, 2026-06-04). See § 2.
  • Critical account-takeover flaw in MISP (CVE-2026-10868, CVSS 9.0) — the threat-intel platform that underpins CERT-EU, GovCERT.ch and most EU national-CERT sharing; a mass-assignment bug lets an authenticated user edit another account (GitHub Security Advisory, 2026-06-04). Patched. See § 2.
  • Five Eyes issue a rare joint bulletin on Chinese intelligence recruiting via LinkedIn and job platforms — targeting cleared personnel, researchers and policy staff; directly relevant to Swiss/EU public-sector personnel security (The Record, 2026-06-03). See § 1.

3. Research & Investigative Reporting

OP-512: China-linked cluster runs a cryptographically-unique, self-reporting IIS web-shell framework against legacy .NET servers [SINGLE-SOURCE]

ReliaQuest documented OP-512, a previously-unreported China-linked espionage cluster targeting internet-facing Microsoft IIS servers running end-of-life .NET Framework 4.0 (ReliaQuest, 2026-06-05) [SINGLE-SOURCE — ReliaQuest original disclosure]. The framework is a three-component web shell — one .aspx file manager plus two .ashx command handlers — that is per-deployment cryptographically unique (RSA signatures and RC4 keys differ per installation), defeating signature-based detection. It carries a timestomping module that matches shell file timestamps to surrounding legitimate IIS artefacts (T1070.006 Timestomp), uses reflective .NET assembly loading to bypass static scanning (T1620), and implements a novel self-reporting beacon: the deployed shell's URL is hex-encoded into a DNS subdomain query issued from w3wp.exe, so the operator is notified of a live shell without actively scanning for it. ReliaQuest found initial access roughly 75 days before the shell was deployed, consistent with patient espionage tradecraft, and notes overlap with the hex-encoded-DNS technique seen in CL-STA-0048 while assessing OP-512 as a separate cluster.

Why it matters to us: Many Swiss and EU public-sector estates still run legacy IIS/ASP.NET portals and intranet apps on .NET 4.0 — exactly OP-512's stated footprint. The detection lesson is concrete: filesystem timestamps are useless for triage here (timestomped), so hunt on behaviour instead — w3wp.exe issuing long hex-string DNS subdomain queries, w3wp.exe spawning cmd.exe/powershell.exe/csc.exe (Sysmon EID 1), reflective-assembly loads, and .aspx/.ashx writes into web roots (Windows Security EID 4663 on inetsrv paths). Hardening: isolate or retire .NET 4.0 servers and apply WDAC/AppLocker to block execution of unsigned web-root artefacts.

4. Updates to Prior Coverage

UPDATE: Miasma supply-chain worm reaches 73 Microsoft GitHub repositories, adds Azure credential collectors

UPDATE (originally covered 2026-06-02): The Miasma worm — the TeamPCP-spawned descendant of the Mini Shai-Hulud lineage first covered against the Red Hat @redhat-cloud-services npm namespace — recompromised the durabletask package and propagated into the Microsoft GitHub estate. On 2026-06-05 GitHub disabled 73 repositories across the Azure, Azure-Samples, Microsoft and MicrosoftDocs organisations in a 105-second automated terms-of-service sweep, taking the entire Azure Durable Task family (.NET, Go, Java, JS, MSSQL, Netherite, protobuf) offline (OpenSourceMalware, 2026-06-05; The Hacker News, 2026-06-06).

The material delta from the 2026-06-02 coverage: the variant adds Azure CLI auth-cache and managed-identity token collectors (earlier Shai-Hulud strains targeted AWS and GitHub), and the recompromise traces to the same durabletask credential foothold from the May TeamPCP incident — i.e. credentials taken in May were never fully revoked. Azure Durable Task is a foundational dependency for Azure Functions / serverless workflows widely consumed in EU public-sector cloud deployments, so the downstream exposure is cloud infrastructure, not just developer machines.

Defender takeaway: audit ~/.azure/ credential stores on developer workstations and CI/CD runners that installed any affected @azure/* package; rotate Azure managed-identity tokens and Kubernetes service-account tokens on those systems; monitor GitHub audit logs for unexpected public-repo creation (the worm's secret-exfil-as-public-repo behaviour is what trips GitHub's automated sweep). Note the worm-vs-defender naming overlap is real here — "Miasma" is the attacker worm, not a tool.

6. Action Items

  • Mitigate Cisco Catalyst SD-WAN Manager now — no patch exists (see § 2 CVE-2026-20245). Actively exploited to root; ACL the management plane to a dedicated management VLAN, enforce MFA for netadmin, rotate Manager credentials, and confirm the earlier pre-auth bypass CVE-2026-20182 is remediated so the unauth-to-root chain is broken. Hunt the CLI audit log and edge-device config-push events.
  • Patch SolarWinds Serv-U to 15.5.4 Hotfix 1 if you run it internet-exposed (see § 2 CVE-2026-28318). Unauthenticated single-request DoS, confirmed exploited; until patched, restrict the SFTP/FTP/HTTP interface exposure.
  • Patch MISP instances to the 2026-06-04 release (see § 2 CVE-2026-10868). Multi-org sharing hubs are highest-priority given the account-takeover + cross-org template-overwrite combination. Pre-patch, monitor UsersController::edit requests where the posted user id ≠ session user id.
  • Lock down npm build pipelines against IronWorm and Miasma (see § 1 and § 4). Enforce npm install --ignore-scripts in CI, pin lockfile integrity, rotate/scope npm publish (incl. Trusted Publishing) tokens, and rotate Azure managed-identity / ~/.azure credentials on any runner that installed an affected @azure/* package. Add bpf()-syscall and Tor-bootstrap egress monitoring on build hosts.
  • Hunt legacy IIS / .NET 4.0 servers for OP-512 behaviourally, not by timestamp (see § 3). Look for w3wp.exe issuing long hex-string DNS subdomain queries and spawning cmd/powershell/csc; isolate or retire EOL .NET 4.0 hosts.
  • Harden against Luna Moth helpdesk-impersonation and physical intrusion (see § 5). Block unauthorised RMM agents via application control, require out-of-band verification of "IT support" callbacks, restrict VDI/VPN to managed devices, and — given the in-person USB vector — review visitor-credentialing/escort policy and USB-write GPO on sensitive endpoints. Brief cleared/research staff on the LinkedIn/job-platform recruitment tradecraft in § 1.

7. Verification Notes

  • Items dropped:
    • CVE-2026-49975 (HTTP/2 Bomb) — surfaced by S1 and S2 but already covered as the full deep dive on 2026-06-04; the in-window BSI WID-SEC-2026-1791 and NCSC-CH advisory 12610 are national-CERT pickup, not a material new development (no new exploitation, no new patch beyond what was already reported), so it is not re-reported under PD-8.
    • Chrome 149 ANGLE sandbox-escape (reported CVSS 9.6) — does not clear a § 2 inclusion gate (no in-the-wild exploitation, no public PoC); the "record 429 vulnerabilities" framing is a vendor-release count, not threat signal. The single sub-agent that surfaced it (S1) had unreliable sourcing (below); the bare CVE id is therefore omitted from this note rather than recorded as fact. Apply Chrome auto-update via MDM as routine.
    • Everest Forms Pro WordPress unauthenticated RCE (reported CVSS 9.8) — only an NVD page (a hard-blocked source) and a single aggregator carried it; no acceptable vendor/research primary was reachable and the exploitation claim was single-source. Dropped pending a verifiable advisory; CVE id omitted as unverified.
    • Altium Enterprise Server path-traversal cluster (reported CVSS up to 10.0, unauth file write) — would clear the CVSS gate but is a niche electronics/defence-engineering product with no observed exploitation and low CH/EU public-sector nexus; the only sourcing was a single sub-agent whose URL ledger proved unreliable (below). CVE ids omitted as unverified.
    • ESET BTMOB Android RAT-as-a-service — primary source dated 2026-05-26 (well outside the 36 h window, and outside the 72 h developing window); Latin-America targeting with low CH/EU nexus.
    • Red Canary "Entra Agent ID → Teams" identity-abuse research — primary dated 2026-06-01, outside the 36 h window; genuinely relevant to CH/EU Copilot/M365 deployments and flagged here for possible pickup if a fresh development lands.
    • Hola Browser update-pipeline cryptominer compromise — real (Sophos/BleepingComputer) but lower operational signal (≈0.1 % of users, cryptominer payload); omitted for focus.
  • Single-source / reduced-confidence:
    • OP-512 (§ 3) is a single-source original disclosure by ReliaQuest; included as research with the lab named, per the PD-5 carve-out for primary research.
    • InfoGuard Q2 2026 Threat Intelligence Report (Iran-resumes / Rockwell FactoryTalk ICS pivot / Russia OT probing) — the InfoGuard primary blog was unreachable and only a German press relay (itiko.de) carried the specific findings; the FactoryTalk-pivot claim could not be independently corroborated, so it is logged here rather than reported as fact.
  • Data-quality note (research sub-agent reliability): S1 returned several fabricated or guessed Source URLs — its JFrog IronWorm URL returned HTTP 404, its OP-512 ReliaQuest URL and several The-Hacker-News slugs were incorrect, and it recorded false 200 statuses for those URLs in the run's URL-liveness ledger (work/<run-id>/url-liveness.tsv). Every S1-derived item retained in this brief (Cisco SD-WAN, SolarWinds Serv-U, IronWorm, Miasma, OP-512) was re-verified against independently-confirmed primaries (NCSC-CH / CISA-KEV bridge, ReliaQuest's correct URL, JFrog Research's correct URL) before inclusion; affected items were dropped.
  • Contradictions: S1 and S3 reported OP-512 with conflicting URLs and differing web-shell detail (S1: three role-specific shells; S3/ReliaQuest: one .aspx + two .ashx with RSA/RC4 per-deployment keying). Resolved in favour of the ReliaQuest source text, which was fetched and verified directly.
  • Coverage gaps: sec-disclosures-edgar (no Item 1.05 8-K filings in window); databreaches-net (HTTP 403, Cloudflare); inside-it-ch (HTTP 403 / empty feed across direct, RSS and Wayback — unreachable this run); sophos-xops (HTTP 503, sixth consecutive run); zdi, recordedfuture-insikt (RSS feed 404); cnil-fr, edpb (no in-window enforcement notices); sekoia (not fetched — time).