ctipilot.ch

CTI Daily Brief — 2026-05-28

Typedaily
Date2026-05-28
GeneratorClaude Opus 4.7 (`claude-opus-4-7`)
ClassificationTLP:CLEAR
LanguageEnglish
Promptv2.60
Items11
CVEs14
On this page

On this page

Tags (27)
Regions (7)
References (39)

0. TL;DR

  • ILIAS LMS — critical patch cluster: unauthenticated TileImageUploadHandler write (CVSS 9.8) plus SOAP access-bypass and multiple SQL-injection bugs. The open-source LMS dominant in Swiss federal training, Swiss/German universities, and DACH public-sector vocational portals shipped nine fixes on 2026-05-27 across the 9.20 / 10.8 / 11.1 branches; NCSC Switzerland published an advisory the same day flagging the SOAP interface as the primary unauthenticated attack surface (ILIAS Security Blog, 2026-05-27; NCSC-CH, 2026-05-27; BSI CERT-Bund WID-SEC-2026-1689, 2026-05-27). Per-bug CVSS not in NVD yet — vendor and BSI advisories are primary.
  • Roundcube Webmail 1.6.16 / 1.7.1 — pre-auth SQL injection in the virtuser_query plugin (CVE-2026-48842, CVSS 8.1) plus three further high-severity flaws. NCSC.ch published an advisory on 2026-05-27 flagging the cluster; Roundcube is the dominant self-hosted webmail across European public administrations and academic institutions (Roundcube Project, 2026-05-24; NCSC-CH, 2026-05-27; Heise, 2026-05-27). The companion bugs cover an LDAP autovalues code-injection (CVE-2026-48844), an SVG-based CSS-sanitisation bypass (CVE-2026-48848) and an SSRF / info-disclosure via crafted SVG animate (CVE-2026-48843).
  • CISA added three supply-chain CVEs to KEV on 2026-05-27 — the Nx Console / TanStack / DAEMON Tools cascade. The Nx Console v18.95.0 VS Code extension compromise (CVE-2026-48027) ultimately traces to a TanStack Router npm supply-chain bug (CVE-2026-45321) that exfiltrated a contributor's GitHub CLI OAuth token; GitHub later confirmed that roughly 3,800 internal repositories and Grafana Labs were also breached. Separately, CVE-2026-8398 covers a six-week trojanisation of signed DAEMON Tools Lite builds 12.5.0.2421–12.5.0.2434 from the official vendor build pipeline. See § 5 (CISA KEV, 2026-05-27; Nx postmortem, 2026-05-19; Help Net Security, 2026-05-21).
  • CERT-PL — three pre-authentication admin-bypass CVEs in Slican PBX (CVE-2026-35087 / -35089 / -35090, all CVSS 4.0 9.3 except -35089 at 8.7). Slican telephony equipment is widely deployed in Polish government, public administration and healthcare and is also sold across Central and Eastern Europe. CVE-2026-35090's hardcoded caller-ID admin bypass on the PSTN modem interface is particularly notable — if remote management is disabled, the call temporarily re-enables it (CERT Polska, 2026-05-27; ENISA EUVD entry, 2026-05-27).
  • Dutch National Police arrested a 35-year-old from Buren over the AFC Ajax data breach. Per BleepingComputer and The Record (citing the Dutch police release), the underlying API access-control flaw and shared keys exposed ~300,000 fan accounts and ~42,000 season-ticket records; Ajax filed Article 33 to the Dutch DPA following the original March 2026 disclosure (BleepingComputer, 2026-05-27; The Record, 2026-05-27; Ajax victim statement, 2026-03-25). The recurring pattern — REST/mobile-app backend with shared-key API access-control — is directly transferable to public-sector citizen portals.
  • CrowdStrike, Google and Shadowserver simultaneously severed all four C2 channels of the GlassWorm developer-targeting botnet. The campaign — active since early 2025, attributed by CrowdStrike to likely Russia-based operators on the basis of CIS-locale exit checks — used Solana blockchain memo fields, BitTorrent DHT, Google Calendar event titles, and traditional VPS C2 in parallel for resilience; takedown required cutting all four at once. Infections persist on developer endpoints and post-compromise credential rotation is required (CrowdStrike, 2026-05-27; TechCrunch, 2026-05-27).

3. Research & Investigative Reporting

MuddyWater / Seedworm — Symantec and Carbon Black document new DLL-side-loading pair via signed Fortemedia and SentinelOne binaries, ChromElevator for Chromium App-Bound Encryption bypass, Node.js orchestration

Symantec's Threat Hunter Team and Broadcom's Carbon Black published findings on 2026-05-12 documenting a Q1 2026 MuddyWater (a.k.a. Seedworm, Static Kitten, MERCURY, TEMP.Zagros — attributed to Iran's Ministry of Intelligence and Security) espionage campaign across at least nine organisations on four continents. The story re-surfaced this run via fresh aggregator coverage on 2026-05-26 (The Hacker News) — included in window on that basis. Named victim categories include industrial and electronics manufacturing, education and public-sector bodies, financial services, and an international airport in the Middle East (Symantec / Broadcom Threat Intelligence, 2026-05-12; The Hacker News, 2026-05-26; Industrial Cyber, 2026-05-13).

The differentiating TTPs from prior MuddyWater coverage are twofold. First, DLL side-loading via two pairs of legitimately signed third-party binaries: Fortemedia audio-driver binary fmapp.exe side-loading a malicious fmapp.dll; SentinelOne's sentinelmemoryscanner.exe side-loading a rogue sentinelagentcore.dll — abuse of a signed security-product binary specifically chosen to bypass signature-based detection. Both malicious DLLs embed ChromElevator, an open-source post-exploitation tool that bypasses Chromium App-Bound Encryption to extract passwords, cookies and payment-card data without triggering AV. Second, orchestration moved to Node.js: node.exe appears as a parent-process ancestor of cmd.exe before any operator commands — i.e. a Node.js script (not a human operator) drives the kill chain. PowerShell scripts pulled from a staging server perform discovery (T1087, T1482), screenshot capture, SAM-hive theft via VSS (T1003.002), and SOCKS5 reverse-proxy tunnelling (T1090.003). A credential harvester calls CredUIPromptForWindowsCredentialsW to display a Windows security dialogue and trick targets into entering credentials. A Kerberos TGT extractor via GSS-API was also observed.

Why it matters to us: signed-binary side-loading abusing a security-product binary is the highest-value evasion class — signature-based controls are bypassed by design. Detection: Sysmon EID 7 image-loads from fmapp.exe or sentinelmemoryscanner.exe outside their expected installation directories; alert on node.exe as a parent of cmd.exe or powershell.exe -enc in non-developer environments; flag CredUIPromptForWindowsCredentialsW calls from non-standard parents. Hardening: AppLocker / WDAC enforcing signed-and-known-path DLL loads; restrict node.exe execution to development OUs.

Microsoft Defender Experts — AI-chatbot search-poisoning extends SEO-poisoning lure; GPU-utility lookalikes drop ScreenConnect, then process-hollowed miners under signed Microsoft binary

Microsoft Defender Experts documented an active cryptojacking campaign dating from March 2026 that uses GPU-utility brand impersonation (CrystalDiskInfo, HWMonitor, Display Driver Uninstaller, FurMark, K-Lite Codec Pack, PDFgear) as initial delivery via SEO poisoning (Microsoft Security Blog, 2026-05-26; The Hacker News, 2026-05-27). The operationally novel evolution is from April 2026: users querying AI chatbots for software-download recommendations were directed to attacker-controlled domains in generated responses — search-poisoning extended into the LLM-generation layer. Delivery chain: (1) fake utility site hosts a ZIP on a gleeze.com subdomain (DDNS via Dynu); (2) ZIP contains the legitimate executable alongside an autorun.dll; (3) DLL side-loading installs vcredist_x64.dll via msiexec.exe — a ScreenConnect packaged installer named to mimic Visual C++ Redistributable; (4) ScreenConnect establishes persistent remote access; (5) the session delivers SimpleRunPE.exe; (6) SimpleRunPE persists via Registry Run keys and scheduled tasks, configures Microsoft Defender exclusions, and uses process hollowing to inject miner code (gminer, lolMiner, SRBMiner-MULTI) into a Microsoft-signed binary. 150+ malicious domains identified since March 2026.

SANS ISC — Akira ransomware kill chain reconstructed entirely from SSLVPN syslog and Windows EVTX, no EDR [SINGLE-SOURCE]

SANS ISC handler Manuel Humberto Santander Pelaez published a forensic walkthrough on 2026-05-27 reconstructing an Akira ransomware intrusion using only two log sources — SSLVPN syslog and Windows EVTX exports — joined by source IP and normalised time (SANS Internet Storm Center, 2026-05-27). [SINGLE-SOURCE] — high-reliability technical primary, but no independent corroboration of the specific kill chain. Initial access (T1078.001 / T1133): non-distributed brute force from a single hosting-provider IP against a single local SSLVPN account that had been deprovisioned in Active Directory but remained provisioned as a local firewall user with no MFA. Discovery: EID 4688 captures nltest.exe /dclist:, net.exe group "Domain Admins" /domain, net.exe group "Enterprise Admins" /domain, whoami.exe /all, and a renamed AdFind.exe variant, all parented explorer.exe → cmd.exe. Credential access (T1558.003 Kerberoasting): a cluster of EID 4769 RC4-encrypted TGS requests for multiple SPNs from a single workstation within a 90-second window. Lateral movement (T1021.001): EID 4624 Logon Type 10 chain from jump host to file server, domain controllers, backup server; EID 4672 special-logon privileges on DC. Defense evasion + impact: EID 1102 security-log clear; sc.exe / net stop of endpoint-protection services (System EID 7036); vssadmin delete shadows /all /quiet.

Why it matters to us: the diary is a forensic-primer for any SOC operating without full EDR coverage — the standard scenario in smaller public-sector entities and DACH commune networks. Concrete takeaways the SANS ISC author makes directly: reconcile local SSLVPN account directories against AD source-of-truth (deprovisioned-in-AD-but-retained-in-firewall is the recurring initial-access pathway in this class); alert on > 50 failed SSLVPN auths from a single source per hour; enable EID 4688 process auditing on every Windows host, set Security log size ≥ 1 GB; alert on RC4 TGS-REP (EID 4769 EncryptionType=0x17) for multiple SPNs from one workstation in a short window; EID 1102 security-log clear is incident-grade in every case; time-sync every host including the firewall to the same NTP source so perimeter-to-endpoint joins remain reliable.

4. Updates to Prior Coverage

No updates this run.

5. Deep Dive — Nx Console / TanStack / DAEMON Tools supply-chain cascade lands three CISA KEV entries

Background. The CISA KEV adds on 2026-05-27 close a chain of disclosures across the preceding three weeks that share a single operational pattern: trusted developer-tooling-publishing pipelines (a maintainer's machine, a vendor build server, a popular VS Code marketplace listing) used to push malicious code to downstream consumers at scale (CISA KEV catalog; Nx postmortem, 2026-05-19; GHSA-c9j4-9m59-847w, 2026-05-18; GHSA-g7cv-rxg3-hmpx, 2026-05-11; Disc Soft Limited, 2026-05-06; Kaspersky, 2026-05-05; Help Net Security, 2026-05-21). This brief has covered the upstream story before — campaign:mini-shai-hulud (TeamPCP) and the 2026-05-24 Packagist Laravel-Lang deep dive both documented the same class of postinstall / publish-token theft chain. The Nx Console / TanStack thread is materially new because three of its CVEs were promoted to CISA KEV on the same day (2026-05-27), confirming active in-the-wild exploitation, and because GitHub's CISO Alexis Wales publicly confirmed that the resulting credential-harvest reached approximately 3,800 internal GitHub repositories along with Grafana Labs.

The TanStack → Nx Console pivot — CVE-2026-45321 and CVE-2026-48027.

The chain begins on or before 2026-05-11 with GHSA-g7cv-rxg3-hmpx (CVE-2026-45321): malicious versions across approximately 42 @tanstack/* npm packages were published with a credential-stealing payload that read locally configured credentials and exfiltrated them — including a Nx contributor's GitHub CLI OAuth token. The Nx postmortem specifically names @tanstack/zod-adapter@1.166.15 as the resolved malicious dependency on the compromised contributor's machine. Mapped to T1195.002 Compromise Software Supply Chain → T1552.001 Unsecured Credentials: Credentials In Files. Seven days later, the attacker used the stolen token to publish Nx Console v18.95.0 (CVE-2026-48027, GHSA-c9j4-9m59-847w) via the legitimate publish path. The malicious version was live on the Visual Studio Marketplace from 12:30 to 12:48 UTC on 2026-05-18 and on Open VSX from 12:33 to 13:09 UTC. Nx Console is a VS Code extension with approximately 2.2 million reported installs; during the live window it fetched an obfuscated second-stage payload that harvested secrets from 1Password vaults, Claude Code configuration files, the developer's npm authentication, additional GitHub PATs, and AWS credentials from ~/.aws/credentials.

The Nx postmortem maps the publish-step compromise cleanly: the stolen GitHub CLI OAuth token had repo and write:packages scope on the maintainer's machine, which was enough to push a new tag and trigger the existing publish workflow without further authentication. The CI workflow ran in GitHub-hosted runners with the regular publish secrets — no additional human-in-the-loop on the publish step. This is the same architectural class of compromise as the earlier TeamPCP mini-shai-hulud chain covered in briefs/2026-05-13.md and the Packagist Laravel-Lang autoloader-backdoor covered in briefs/2026-05-24.md: a stolen developer credential turned into automated downstream-publish without secondary review.

CVE-2026-8398 — DAEMON Tools Lite signed-build trojanisation.

CVE-2026-8398 covers a separate but parallel compromise of the official Disc Soft Limited build pipeline. DAEMON Tools Lite versions 12.5.0.2421 through 12.5.0.2434, distributed from 2026-04-08 through 2026-05-05, contained trojanised DTHelper.exe, DiscSoftBusServiceLite.exe, and DTShellHlp.exe binaries signed with a valid AVB Disc Soft code-signing certificate and beaconing to attacker infrastructure on activation (Disc Soft Limited, 2026-05-06; Kaspersky, 2026-05-05). Kaspersky identified thousands of attempted secondary-payload installs against affected hosts during the six-week distribution window. The Disc Soft vendor advisory confirms the build infrastructure itself was compromised — the malicious binaries went through the legitimate signing path, not via a publication-credential theft. Safe version: 12.6.0+. The CVE moved to CISA KEV on 2026-05-27 on the strength of in-the-wild exploitation evidence Kaspersky and other vendors contributed.

Downstream impact — what GitHub and Grafana Labs publicly confirmed.

Help Net Security reported on 2026-05-21 (Help Net Security, 2026-05-21) that GitHub CISO Alexis Wales had publicly named the malicious Nx Console v18.95.0 extension as the root-cause vector for the earlier 2026 GitHub breach in which ~3,800 internal repositories were exfiltrated. Grafana Labs separately reported a breach traced to the same vector. The downstream-victim pattern is operationally significant: a single malicious VS Code extension live for 18 minutes was enough to reach internal corporate networks via developer-endpoint credential harvesting.

Detection and hardening — what to push to operators today.

ATT&CK mapping: T1195.002 Compromise Software Supply Chain (publish-path compromise), T1552.001 Unsecured Credentials: Credentials In Files (1Password / ~/.aws/credentials / Claude Code config harvesting), T1530 Data from Cloud Storage Object (downstream CI/CD secret reuse), T1567 Exfiltration Over Web Service.

Detection: EDR parent-process lineage vscode.exe / cursor.exe / windsurf.exe spawning node.exe with outbound network egress to non-standard hosts (Extension Host Worker is the legitimate child; secondary node.exe workers fetching obfuscated payloads are not); audit VS Code extension marketplace installs across the developer estate against an approved-extensions allowlist; flag any installation of nrwl.angular-console (the Nx Console publisher ID) at a version pinned to 18.95.0. For DAEMON Tools Lite: hunt for DTHelper.exe or DTShellHlp.exe invocations with parent-process or file-modify timestamps inside the 2026-04-08 → 2026-05-05 window and a hash that does not match the post-12.6.0 reference set (use the vendor's published file-list, do not redistribute hashes here).

Hardening: enforce an organisational policy controls list for VS Code / Cursor / Windsurf extensions (the marketplaces do not enforce mandatory code-signing on extensions); pin npm dependencies with lockfile + --ignore-scripts for CI/CD builds; require human approval for any package that adds or modifies postinstall / preinstall / install scripts; rotate every CI/CD secret, npm token, GitHub PAT, and AWS access key accessible from any host that ran an affected Nx Console version between 2026-05-18 12:30 and 13:09 UTC. For developer endpoints, treat any host that installed an extension from Open VSX or VS Code Marketplace in that window as potentially compromised — credential rotation is not optional.

6. Action Items

(Derived from this brief's content only.)

  • Inventory and patch ILIAS deployments to 9.20 / 10.8 / 11.1 today. Two critical access-control bugs (TileImageUploadHandler unauth file-write CVSS 9.8; MyStaff post-auth SQLi CVSS 9.3) plus seven further high-severity issues — see § 1. Interim mitigation per NCSC.ch: disable the SOAP interface (/webservice/soap/) on any deployment that does not require it for enterprise HR / SIS integration. Reference: ILIAS Security Blog, NCSC-CH 12599.

  • Roundcube — upgrade to 1.6.16 LTS or 1.7.1, today if virtuser_query is enabled. Pre-auth SQL injection in the virtuser_query plugin (CVE-2026-48842, CVSS 8.1) plus three high-severity companion bugs — see § 2. Reference: Roundcube Project.

  • Slican PBX — patch to IPx 6.61.0040 / CCT-1668 + MAC-6400 6.56.0430 / CXS-0424 6.30.0510 / NCP 1.24.0250. Three unauthenticated admin-bypass CVEs (CVE-2026-35087 / -35089 / -35090). If you cannot patch immediately, restrict admin-protocol access by source IP at the upstream firewall and disable the PSTN modem management interface — CVE-2026-35090's caller-ID bypass temporarily re-enables remote management even when configured off. Reference: CERT Polska.

  • Inventory VS Code / Cursor / Windsurf extensions across the developer estate against an approved-extensions allowlist; pin Nx Console to ≥ 18.100.0 and rotate every CI/CD secret accessible from a host that ran Nx Console v18.95.0 between 2026-05-18 12:30 and 13:09 UTC. See § 5 for the full chain — TanStack → Nx Console → GitHub / Grafana. CISA KEV adds 2026-05-27 confirm active in-the-wild exploitation. Reference: Nx postmortem.

  • DAEMON Tools Lite — replace versions 12.5.0.2421–12.5.0.2434 with ≥ 12.6.0 on every host they were installed on. Trojanised builds signed by the legitimate vendor certificate during the 2026-04-08 → 2026-05-05 window — see § 5. Reference: Disc Soft Limited security notice.

  • Hunt for GlassWorm-class developer infections in the network — focus on the dev estate. Even after the C2 takedown the endpoints remain infected; rotate every credential and CI/CD secret accessible from a developer host that installed extensions from VS Code Marketplace or Open VSX between early 2025 and 2026-05-26. Detection concepts in § 1. Reference: CrowdStrike.

  • Reconcile local SSLVPN account directories against AD source-of-truth; enforce MFA on every SSLVPN account regardless of directory. SANS ISC's Akira walkthrough (see § 3) confirms deprovisioned-in-AD-but-retained-in-firewall accounts as the primary initial-access pathway for this class. Alert on >50 failed SSLVPN authentications from a single source per hour; set Windows Security log size ≥ 1 GB on every host so EID 4688 discovery-phase evidence does not roll off before incident response arrives.

  • Defenders running large hypervisor estates — separate the recovery plane from the production identity boundary. The MOIS / Ababil-of-Minab LACMTA pattern (see § 1) explicitly targets backup and VM-lifecycle APIs for destruction in parallel with exfiltration. Treat backup-orchestration admin access as a separate identity boundary with MFA on backup-job execution and a tested air-gapped restore path that does not depend on the same identity provider as production.

7. Verification Notes

  • Items dropped — vulnerabilities that did not clear § 2 inclusion gates.
    • CVE-2026-9256 / CVE-2026-42945 — NGINX double rewrite-module heap buffer overflow. S1 surfaced these as actively-exploited per NCSC-NL CSAF (NGINX meldt bekend te zijn met (pogingen tot) misbruik), but the freshest sources are dated 2026-05-22 (NGINX vendor advisory and oss-security mailing list) and 2026-05-18 (NCSC-NL) — both outside the 40-h recency window with no in-window corroborator surfaced. Dropped to § 7 rather than included as a stale exploitation note. Patch is still relevant — 1.31.1+ or 1.30.2+ — defenders running unpatched NGINX should not wait for a future brief to act.
    • CVE-2026-45659 — Microsoft SharePoint Server CWE-502 deserialization RCE (CVSS 8.8). S1 + S2 both surfaced; NCSC.ch flagged on 2026-05-26 in CSH 12594 (Microsoft MSRC; NCSC-CH post 12594; Help Net Security, 2026-05-26). Did not clear § 2 inclusion gates: post-auth (Site Member, PR:L), no CISA KEV, no ENISA EUVD exploited=true, no in-the-wild exploitation confirmed, CVSS 8.8 below the 9.0 EUVD-critical floor, and no public PoC reported. Defenders running on-prem SharePoint should still apply the May 2026 CU (SE 16.0.19725.20280 / SP2019 16.0.10417.20128 / SP2016 16.0.5552.1002) — the prior history of rapid weaponisation of SharePoint deserialization gadget chains supports priority patching even without current exploitation evidence.
    • CVE-2026-27771 — Gitea container-registry access-control failure (~30,000+ deployments). S1 + S3 both surfaced (NoScope, 2026-05-25; The Hacker News, 2026-05-27). Patched in Gitea v1.26.2 (released 2026-05-20). Did not clear § 2 gates — unauthenticated image-pull (data-exposure), not RCE; no KEV / EUVD-critical / confirmed in-the-wild exploitation. Forgejo (the fork used by Codeberg and many EU academic instances) confirmed affected. The four-year window of exposure means retrospective log review for unauthenticated /v2/<namespace>/<repo>/{manifests,blobs} GETs is warranted on any self-hosted Gitea / Forgejo instance running below 1.26.2; rotate any secrets embedded in container images that were stored as private.
    • Grandoreiro + BTMOB Android RAT (WatchGuard / ESET, 2026-05-26). Surfaced by S3. Banking-only sector (Portugal / Spain / Brazil / Europe consumer-banking customers); did not clear the daily-relevance bar for a Swiss/EU public-sector SOC audience. Mentioned here so the next run does not re-surface it as new.
    • Catalin Dragomir / Oregon OEM sentencing (TheRecord, 2026-05-27). Surfaced by S4. 2021 access-broker sentencing is procedurally significant but the underlying breach is years old and the operational signal — emergency-management network as access-broker target class — is generic; below the daily inclusion bar. Logged here for next-run dedup.
  • [SINGLE-SOURCE] items. § 3 SANS Internet Storm Center Akira kill-chain reconstruction — single primary publisher, but a high-reliability technical forensic primer; included per PD-5 carve-out (HIGH-reliability primary research source). No defender action flows from the item that needs a second confirmation.
  • Reduced confidence — only aggregator sources. § 1 FBI FLASH CSA 260526 (Silent Ransom Group physical-USB tactic) — the FBI IC3 primary PDF (https://www.ic3.gov/CSA/2026/260526.pdf) returned HTTP 403 to the routine UA and to the bridge fetcher; the three cited sources (CyberScoop, The Record, Help Net Security) are all news aggregators paraphrasing the same FBI advisory. The advisory itself is the substantive primary; operators should fetch the IC3 PDF directly from a desktop browser session to confirm the verbatim text before acting.
  • MuddyWater / Symantec primary-source date resolution. S1 reported the Symantec primary as 2026-05-22; S3 reported it as 2026-05-26. Phase 5.7 iteration 1 independently extracted the actual Symantec publication date as 2026-05-12 (and Industrial Cyber as 2026-05-13). § 3 has been re-dated to those values; The Hacker News (2026-05-26) is the in-window publication that pulled the story back to surface and is the reason the item appears in this brief at all. Under PD-7's "freshest source in window" reading the item remains in scope; readers should note the underlying Symantec research is two weeks old.
  • Contradictions across linked sources. Germany Cybersicherheitsstärkungsgesetz staffing figure — onvista (dpa) reports "more than 350 new positions" across BKA / BSI / Bundespolizei plus ~€50 million per year; t-online reports a notably smaller initial figure (37 additional employees). The brief carries the dpa-sourced ~350 framing because the onvista/dpa wire is more likely to reflect the cabinet's published bill text; the t-online figure may refer to one specific agency or a phased intake. Operators tracking the bill's progression should follow the Bundestag-stage publication for the authoritative position count.
  • Stalled or non-returning sub-agents. None — all four cti-research sub-agents returned within the 30-min hard cap (S1: 527 s; S2: 496 s; S3: 542 s; S4: 560 s).
  • Verification loop. Phase 5.7 ran four iterations (Opus → Sonnet → Opus → Sonnet, per the v2.47 model-rotation contract). Iteration 4 returned NEEDS_FIXES with one F3 (citation-does-not-support-claim) finding — the AFC Ajax TL;DR bullet retained the iter-3-flagged "granted himself access" framing after the § 1 body had been re-paraphrased. That TL;DR-vs-body inconsistency was remediated post-iter-4 (TL;DR rewritten to match the § 1 body's neutral phrasing). Per v2.50 early-exit (truth + editorial ≤ 2 AND no F1/F4), the brief publishes with verification_residual_count = 1 (the iter-4 F3 finding, since fixed in place — same disposition as a cap-breach reached at iter 4 rather than at iter 5). Two F11 advisories (Slican "hardcoded" / "widely deployed in Polish public sector" framing exceeds CERT-PL's direct language; ILIAS vendor blog list-page render date 2026-05-26 vs NCSC-CH 12599 publish stamp 2026-05-27) were deferred as defensible and non-load-bearing.
  • Coverage gaps: databreaches-net (HTTP 403, sixth consecutive run — covered via BleepingComputer / TheRecord / SecurityWeek; not a real gap this run); inside-it-ch (HTTP 403, fifth consecutive run — no exclusive in-window CH-tech story surfaced via alternates); sophos-xops (HTTP 503, fifth consecutive run — no Sophos research story surfaced elsewhere in window); anssi-fr (avis-recent newest item 2026-05-20 — outside window; actu-recent stale at October 2025); ncsc-uk (RSS items 2022–2025 only, no in-window content); cisa-news (no fresh in-window emergency directive); apple-security, oracle-cpu, chrome-releases (no in-window vendor publication); dfirreport, sekoia (RSS empty for window).
  • New candidate source surfaced — gambit-security. Israeli threat-intelligence firm with primary MOIS / Iran-linked research; the Ababil-of-Minab attribution report (2026-05-26) on the LACMTA breach is the discovery event. Surfaced by S4. Added to sources/sources.json as status: "candidate" per the one-candidate-per-run rule; promote after 3 successful contributing fetches.
  • NoScope, the discoverer of CVE-2026-27771 (Gitea private container exposure), also surfaced as a candidate source by S3 but is deferred per the one-candidate-per-run rule. Carried as a coverage-gap note for next-run consideration.
  • Hardcoded sinkhole IP avoided. CrowdStrike's post-takedown GlassWorm sinkhole at 164.92.88[.]210 is the operationally useful artefact for retrospective detection, but the brief avoids IPs per PD-3 (no IOCs). Operators acting on the GlassWorm § 1 item should obtain the sinkhole address directly from the CrowdStrike post and apply it in their network telemetry.