On this page
On this page
- 0. TL;DR
- 1. Active Threats, Trending Actors, Notable Incidents & Disclosures
- 2. Trending Vulnerabilities
- 3. Research & Investigative Reporting
- 4. Updates to Prior Coverage
- 5. Deep Dive — Keycloak JWT algorithm confusion (CVE-2026-11800): forging federated identity in the EU public sector's dominant IdP
- 6. Action Items
- 7. Verification Notes
Tags (22)
Regions (6)
References (23)
- CVE-2026-58053
- CVE-2026-55200
- CVE-2026-11800
- CVE-2026-55199
- CVE-2026-9099
- CVE-2026-9800
- CVE-2026-10712 ×3
- CVE-2026-35273 ×9
- NAIC breached via Oracle PeopleSoft zero-day; ShinyHunters publishes 3.1 TB of insurance-regulatory data
- Jaguar Land Rover Aug-2025 ransomware: NYT first names Russian state-linked group; UK CMC Category-3 systemic event
- Netcraft: Bluekit PhaaS uses Browser-in-the-Middle (rrweb DOM streaming) to defeat FIDO2 and DBSC
- Unit 42: CL-STA-1062 deploys TinyRCT .NET backdoor via AppDomainManager injection
- Cisco Talos: Windows COM abuse (ITaskService/BITS/WMI/DCOM) as EDR-evasion primitives
- Island: 'BadBlocker' — 11M-user Chrome ad-blocker one server call from arbitrary JS on any site
- NCSC-NL — Security Advisories (RSS)
- BSI Germany — CERT-Bund WID (RSS)
- ENISA
- GitHub Advisory Database
- Cisco Talos
- Palo Alto Networks Unit 42
- VulnCheck
- Keycloak Project (security advisories / release notes)
- Netcraft
0. TL;DR
- NAIC — the standard-setting body for all 50 US state insurance regulators — confirms a breach via an Oracle PeopleSoft zero-day; ShinyHunters published ~3.1 TB of insurance regulatory and credit-rating-agency data, and rating-agency feeds paused, forcing NAIC to suspend assigning investment-risk designations. Part of a 100+ org PeopleSoft zero-day campaign; any organisation running Oracle PeopleSoft should verify patch status against the campaign (NAIC, 2026-06-26). See § 1.
- Gitea
act_runnercontainer-hardening bypass (CVE-2026-58053, CVSS 9.4, public PoC) lets any contributor with repo write access escape aprivileged: falseCI container to root on the host — self-hosted Gitea + Docker CI is common in Swiss/EU public-sector and academic IT (VulnCheck, 2026-06-27). See § 2. - libssh2 heap out-of-bounds write (CVE-2026-55200, CVSS 9.2) now has a public PoC confirming code execution; it is embedded in curl, PHP, WinSCP, FileZilla and many network appliances — a malicious/compromised SSH server can corrupt a connecting client's heap (NCSC-NL, 2026-06-24). See § 2.
- Keycloak 26.6.4 patches a JWT algorithm-confusion flaw (CVE-2026-11800, CVSS 8.1) that lets an attacker with any valid client credential forge assertions and impersonate any federated user — including admins — Keycloak is the dominant open-source IdP across EU public administration (Keycloak Project, 2026-06-26). Today's deep dive — § 5.
- A New York Times investigation provides the first named attribution for the August 2025 Jaguar Land Rover ransomware attack — a Russian state-linked criminal group — in an incident that halted JLR production for ~six weeks and is estimated at ~£1.9 bn / $2.5 bn in UK economic impact. Attribution is the investigators' assessment, not an official UK government statement (TechCrunch, 2026-06-26). See § 1.
1. Active Threats, Trending Actors, Notable Incidents & Disclosures
NAIC breached via Oracle PeopleSoft zero-day; ShinyHunters publishes 3.1 TB of US insurance-regulatory data and rating-agency feeds pause
The National Association of Insurance Commissioners (NAIC) — the US standard-setting body governing all 50 state insurance regulators — confirmed on 2026-06-26 that an unauthorised party gained access to part of its environment on 2026-06-11 by exploiting an Oracle PeopleSoft vulnerability that was unknown to the vendor at the time, then used the PeopleSoft foothold to obtain credentials that pivoted into NAIC data-storage areas (NAIC, 2026-06-26). The flaw is reported as CVE-2026-35273, a critical unauthenticated remote-code-execution vulnerability in Oracle PeopleSoft Enterprise PeopleTools 8.61 and 8.62 (Insurance Business Mag, 2026-06-24). NAIC states the access path has since been blocked and remediated and that the FBI plus external forensics are engaged. The extortion group ShinyHunters claimed responsibility on 2026-06-18 and by 2026-06-25 had published the data, which corroborating reporting puts at ~3.1 TB (TechRadar, 2026-06-26); the corpus is reported to include insurer statutory financial-reporting documents and files from major credit-rating agencies (Insurance Journal, 2026-06-25). NAIC says it has not confirmed ShinyHunters' claim to have taken SERFF, OPTins, UCAA, EDP and RDC, and that employee PII, EFT, policyholder and producer data were not accessed. The operationally significant consequence: several rating agencies paused their data feeds to NAIC, forcing it to temporarily suspend assigning investment-risk designations to insurer portfolios — a direct disruption to US insurance-sector solvency monitoring. The incident is reported as part of a broader PeopleSoft campaign affecting 100+ organisations (Insurance Business Mag, 2026-06-24).
Why it matters to us: Oracle PeopleSoft is widely deployed for HR/finance in European and Swiss public-sector and large enterprises; the kill chain here is T1190 (exploit a public-facing PeopleSoft app) → T1078 (abuse the obtained credentials/session to pivot to data stores) → T1567 (web-service exfiltration). Verify PeopleSoft patch status against the in-the-wild zero-day campaign, segment PeopleSoft data-bus/integration accounts to least privilege, and put DLP/volume alerting on bulk export from PeopleSoft repositories. EU/Swiss insurance supervisors (EIOPA, national NCAs) and reinsurers whose data is in the rating-agency corpus should treat affected feeds as potentially tampered until NAIC confirms integrity restoration.
NYT investigation gives first named attribution for the Jaguar Land Rover ransomware attack — a Russian state-linked criminal group
A New York Times investigation published 2026-06-26 provides the first named attribution for the August–October 2025 ransomware attack on Jaguar Land Rover (JLR): investigators including the FBI, the UK National Crime Agency, NCSC, Google Mandiant and Palo Alto Networks now attribute the core intrusion to a Russian state-linked criminal group (Microsoft is reported to have named the group to investigators) (TechCrunch, 2026-06-26; The Next Web, 2026-06-26). The attribution is the investigators' assessment relayed through journalism — the UK government has not made it official, and investigators say they cannot establish whether the group acted on Kremlin orders, with tacit approval, or independently. The attack halted JLR manufacturing for roughly six weeks and disrupted 5,000+ supply-chain businesses, with UK economic damage estimated at ~£1.9 bn ($2.5 bn). Investigators also found a separate Jordanian actor ("Rey") independently inside JLR networks, illustrating multi-actor opportunistic access to the same under-segmented victim.
2. Trending Vulnerabilities
CVE-2026-58053 — Gitea `act_runner` Docker backend: container-hardening bypass to host escape (CVSS 9.4, public PoC)
Gitea act_runner through 0.262.0 with the Docker backend passes the workflow-defined container.options string straight into Docker's HostConfig for the job container. When an operator hardens the runner with privileged: false, the code forces only the Privileged flag off but still merges the rest of container.options unchanged — so options such as --pid=host, --cap-add=SYS_PTRACE, --security-opt=seccomp:unconfined or arbitrary bind mounts pass through, allowing any user with write access to a repository whose workflows run on that runner to escape to the host as root despite the hardening (VulnCheck, 2026-06-27; ENISA EUVD EUVD-2026-58053, 2026-06-28). ENISA EUVD scores it CVSS 4.0 9.4 and a public PoC is referenced. Technique class: T1611 Escape to Host via Docker HostConfig injection → T1068. Prerequisite is write access (or accepted external contribution) to a repo whose workflows execute on a Docker-backed runner configured privileged: false — the common hardened setting, which is what makes this dangerous. Self-service CI on internal Gitea + Docker is common in Swiss/EU public-sector and academic IT. Detection: watch Docker daemon audit logs for containers launched with unusual HostConfig flags (pid_mode=host, non-baseline cap_add, custom seccomp); review CI workflow-YAML diffs from external contributors for container.options injection. Mitigation now (vendor fix act_runner >= 0.263.0 was pending at advisory time): strip or allowlist container.options at the runner policy layer, require approval for fork/external-contributor workflow runs, and use a kernel-isolation runtime (e.g. gVisor) for untrusted CI.
CVE-2026-55200 — libssh2 heap out-of-bounds write in `ssh2_transport_read()` with public PoC; companion pre-auth DoS CVE-2026-55199
CVE-2026-55200 is a heap out-of-bounds write (CWE-680 integer-overflow-to-buffer-overflow) in libssh2's ssh2_transport_read(): the packet_length field in an SSH transport packet is not bounds-checked before allocation, so a malicious or compromised SSH server can send a crafted length to corrupt a connecting client's heap — leading to DoS or, where ASLR is absent, potential remote code execution. NCSC-NL updated advisory NCSC-2026-0210 on 2026-06-24 to note that a public PoC has appeared confirming code execution under specific conditions; the GitHub advisory scores it CVSS 9.2 (NCSC-NL, 2026-06-24; GitHub Advisory GHSA-r8mh-x5qv-7gg2, 2026-06-23). The companion flaw CVE-2026-55199 (CVSS 8.2, CWE-835 infinite loop via a crafted SSH_MSG_EXT_INFO extension count → pre-auth CPU exhaustion/DoS) is also unfixed in 1.11.1. libssh2 is embedded in curl, the PHP ssh2 extension, FileZilla, WinSCP, Bitvise and many network appliances, so downstream exposure depends on vendor uptake. Technique class: T1190 (client-side, when tricked into connecting to an attacker-controlled server) for the OOB write; T1499.004 for the DoS. Affected: libssh2 ≤ 1.11.1; fixes are commit 97acf3df (55200) and 1762685 (55199), with no tagged release (1.11.2) yet. Detection/hardening: hunt heap-corruption crashes in processes using libssh2 (PHP-FPM, curl, scp wrappers); inventory embedded libssh2 versions in appliances/tooling; confirm ASLR is enabled (/proc/sys/kernel/randomize_va_space = 2) to raise the bar on the code-execution path; constrain automation hosts to known SSH endpoints.
3. Research & Investigative Reporting
Netcraft: Bluekit PhaaS uses Browser-in-the-Middle to defeat FIDO2 and Device Bound Session Credentials
Netcraft published a technical breakdown (2026-06-25) of Bluekit, a phishing-as-a-service platform first documented by Varonis Threat Labs (2026-04-29) and now seen by Netcraft at scale (~70 active hostnames in a single week) (Netcraft, 2026-06-25; Varonis, 2026-04-29). Bluekit's distinguishing technique is Browser-in-the-Middle (BitM): instead of proxying the victim's HTTP traffic the way Evilginx/AiTM kits do (which leaves session-fingerprint mismatches), it runs a real automated browser on attacker infrastructure and streams its live DOM to the victim over WebSocket using the open-source rrweb DOM-serialisation library. The victim's keystrokes and clicks are relayed into the attacker's browser and executed against the genuine site, so the session is created in and owned by the attacker from the start — which is why Device Bound Session Credentials (DBSC, which bind tokens to the legitimate device's keys) provide no protection, and why FIDO2/WebAuthn is bypassed (the attacker's browser completes the relying-party challenge on the victim's behalf). Anti-analysis: per-load randomised CSS filter values to defeat screenshot pixel-hashing, >1 MB rotating obfuscated JS bundles, brand-impersonating CAPTCHA, and WebRTC IP-mismatch checks to spot analyst proxies. Detection concepts: rrweb presence outside legitimate analytics; WebSocket streams of binary/encrypted DOM diffs to unexpected origins; sub-second form-submission round-trip latency characteristic of BitM relay; randomised CSS filter rules on top-level HTML. Relevant because Microsoft 365 / Entra ID tenants — including Swiss and EU public-sector ones — are named targets, and BitM degrades the "phishing-resistant MFA solves this" assumption.
Unit 42: Chinese-speaking cluster CL-STA-1062 deploys the new TinyRCT .NET backdoor against SE-Asian government and energy targets via AppDomainManager injection
Palo Alto Unit 42 (2026-06-25) documented CL-STA-1062, a Chinese-speaking cluster overlapping with Cisco Talos's UAT-7237, targeting government and state-owned energy infrastructure across Southeast Asia (Unit 42, 2026-06-25; The Hacker News, 2026-06-26). Initial access is via internet-facing web apps and ASPX web shells (T1505.003), pivoting to a custom .NET backdoor, TinyRCT, delivered through AppDomainManager injection (T1574.014): a benign signed chrome_setup.exe ships in a ZIP alongside a malicious chrome_setup.exe.config, causing the .NET CLR to load MyAppDomainManager.dll from the same directory and bootstrap TinyRCT in-process — no child process, so it is low-visibility to EDR. TinyRCT beacons over HTTP with AES-128-CBC payloads, supports command execution via cmd.exe, chunked file exfiltration, and screen capture, and self-terminates unless run from %LOCALAPPDATA% or %USERPROFILE%\Downloads (anti-sandbox). Observed tooling includes Mimikatz, JuicyPotato and SoftEther VPN masqueraded as vmtools.exe. The defender value is the technique: T1574.014 AppDomainManager injection is widely under-detected, and the same web-shell-to-in-process-.NET pattern is directly applicable to European public-sector web estates. Hunt for .NET .config files written into user-writable directories adjacent to signed executables, and DLL loads of MyAppDomainManager.dll from a signed PE's own directory (Sysmon EID 7).
Cisco Talos: a field guide to Windows COM abuse — ITaskService, BITS, WMI and DCOM as EDR-evasion primitives [SINGLE-SOURCE]
Cisco Talos published a reverse-engineering primer (2026-06-25) on how Windows threats weaponise Component Object Model (COM) interfaces to hide operations inside legitimate service call stacks (Cisco Talos, 2026-06-25). Four technique classes with a shared detection gap — function calls routed through vtable indirection rather than direct API imports limit EDR visibility: ITaskService/ITaskScheduler persistence creates scheduled tasks with no visible schtasks.exe (T1053.005); IBackgroundCopyJob (BITS) moves C2/files attributed to the trusted BITS service process (T1197); IWbemLocator/WMI blends discovery into svchost.exe (T1082, T1518.001); and DCOM/IDispatch enables remote object activation for lateral movement (T1021.003). Families studied include Gh0stRAT (ITaskService persistence), Attor (BITS C2 + WMI), Qakbot (WMI) and WarmCookie (ITaskScheduler 1.0). The actionable takeaway for detection engineers: scheduled-task-creation rules keyed on schtasks.exe/PowerShell miss COM-based task creation, which emits different event logs; build coverage for task creation where the creating image is unexpected, WMI activity from non-system parents, and BITS jobs created by non-svchost processes.
Island: "BadBlocker" — an 11M-user Chrome ad-blocker is one server config change away from arbitrary JavaScript on any site
Island researchers documented (2026-06-25) a dormant but architecturally complete arbitrary-JavaScript-execution capability in "Adblock for YouTube" (11M+ installs) (Island, 2026-06-25; The Hacker News, 2026-06-25). The extension fetches config every 24 hours; a server-controlled scriptletsRules field can activate a "create-element" scriptlet that appends an externally-sourced <script> to the DOM via a TrustedTypes policy that bypasses the browser's own script-injection guard. Because the extension declares <all_urls> host permissions but only checks whether the string youtube.com appears anywhere in the URL (not as the hostname), a lure such as https://bank.example.com/search?q=youtube.com passes the check — so an injected script could run in authenticated banking, admin-panel or enterprise-SaaS sessions with full DOM and credential access (T1176 Browser Extensions; T1056 Input Capture). Island demonstrated a Salesforce-data-exfiltration PoC; no malicious payload was live at analysis time, but sister extensions were previously removed by Google for actual malware. Defender concepts: flag browser extensions making config-fetch HTTPS requests outside their declared purpose; audit <all_urls> extensions against business need; enforce extension allowlisting via browser management policy.
4. Updates to Prior Coverage
No qualifying updates this run. The in-window developments on previously-covered stories (Turla STOCKSTAY, the Miasma/"Mini Shai-Hulud" npm worm, the Ubiquiti UniFi OS KEV chain) carried no material new delta beyond what the last two briefs already reported — see § 7.
5. Deep Dive — Keycloak JWT algorithm confusion (CVE-2026-11800): forging federated identity in the EU public sector's dominant IdP
Background. JWT algorithm confusion is a long-known token-forgery class — public research dating to the mid-2010s showed that if a verifier trusts the attacker-controlled alg header field, an attacker can substitute the signing algorithm (classically RS256→HS256, treating the public RSA key as an HMAC secret, or downgrading to alg: none) to forge a validly-"signed" token. The defensive consensus has been settled for years: pin the accepted algorithm server-side and never let the token dictate it. CVE-2026-11800 is notable not because the class is new but because it lands in Keycloak, the dominant open-source identity-and-access platform across European public administration (and the upstream of Red Hat Build of Keycloak / Red Hat SSO), where a token-layer bypass collapses the entire federated-identity trust boundary.
What the flaw is. Keycloak 26.6.4 (released 2026-06-26) patches eight CVEs; the headline issue is CVE-2026-11800 (CVSS 8.1, CWE-347 Improper Verification of Cryptographic Signature): an attacker holding any valid client credential in a realm can forge an assertion in the JWT Authorization Grant flow by manipulating the algorithm field, bypassing signature verification to mint unauthorised access tokens and impersonate any federated user linked to the affected identity provider — including administrators (Keycloak Project, 2026-06-26; GitHub Advisory GHSA-gqj5-2xp5-3qmp, 2026-06-25; BSI WID-SEC-2026-2093, 2026-06-26). The prerequisite — a single low-privilege registered OAuth client — is a low bar in a multi-tenant realm with many onboarded applications.
Why the release matters beyond the headline. The same 26.6.4 release fixes CVE-2026-9800 (CVSS 8.1, CWE-1025 policy-enforcer authorization bypass: an authenticated attacker who places the configured access-denied-page path into a request URL as a path segment or query parameter bypasses role/scope/UMA permission checks) and a privilege-escalation path from group-admin to realm-admin (CVE-2026-9099), plus information-disclosure, XSS, disabled-client-re-enablement and scope-mapping-bypass issues. CVE-2026-11800 maps to T1550.001 (Application Access Token abuse) and, where MFA is policy-enforced at the IdP, T1556.006 (the token issuer is bypassed, so MFA is moot); CVE-2026-9800 maps to T1078.004 valid-account abuse with elevated privilege.
Affected / fixed. Upgrade to Keycloak 26.6.4 per the project release notes; Red Hat Build of Keycloak users apply the matching advisories (Red Hat issued RHSA errata for RHBK alongside the upstream release). Treat any internet-reachable Keycloak admin or token endpoint as priority.
Hunt and detection concepts (no IOCs). In Keycloak's own event log, alert on token issuances where the JWT alg does not match the realm's configured signature algorithm (e.g. HS256 appearing on a realm configured for RS256/ES256), and on CODE_TO_TOKEN/CLIENT_AUTH events that resolve to a user the requesting client should not be able to assert. For the policy-enforcer bypass, review access-enforcer logs for requests containing the access-denied-page path as a query parameter or trailing path segment. Correlate admin REST calls (POST /admin/realms/{realm}/clients, role-mapping changes) against accounts that were previously only group-admins (the CVE-2026-9099 vector). Pipe these into the SIEM as identity-tier detections, not just app logs.
Hardening / mitigation. Beyond patching: enforce an explicit algorithm allowlist in realm OIDC settings so the alg field cannot be downgraded (none/HS256 must be rejected where asymmetric signing is expected); review group-to-role mappings for any realm-admin delegation; tighten Registration Access Token expiry; and keep the admin console off the public internet. The structural lesson for any IdP — Keycloak or not — is that the token verifier must own the algorithm decision; the token must never be allowed to choose how it is verified.
6. Action Items
- Constrain Gitea
act_runnernow (§ 2, CVE-2026-58053): on Docker-backed runners, strip or allowlistcontainer.optionsat the runner policy layer and require approval for external-contributor/fork workflow runs; upgrade toact_runner >= 0.263.0when released. Public PoC + CVSS 9.4 + the bypass specifically defeats theprivileged: falsehardening operators rely on. - Inventory and remediate libssh2 (§ 2, CVE-2026-55200 / -55199): identify embedded libssh2 ≤ 1.11.1 in curl, PHP ssh2, WinSCP/FileZilla and appliances; apply downstream vendor fixes / the patched commits; confirm ASLR is enabled on hosts running SSH-client automation; restrict automation to known SSH endpoints.
- Upgrade Keycloak to 26.6.4 and lock the algorithm allowlist (§ 5, CVE-2026-11800 / -9800): reject
none/HS256where asymmetric signing is expected, audit group-to-realm-admin mappings, keep the admin console off the public internet, and add identity-tier SIEM detections foralg-mismatched token issuance. Red Hat Build of Keycloak: apply the matching RHSA errata. - Verify Oracle PeopleSoft exposure and hunt for the pivot pattern (§ 1, NAIC): confirm patch status for CVE-2026-35273 (pre-auth RCE in PeopleTools 8.61/8.62) against the in-the-wild campaign, least-privilege PeopleSoft integration/service accounts, and alert on bulk export volumes from PeopleSoft data-bus repositories (DLP + off-hours staging).
- Patch PowerDNS Recursor / DNSdist on the normal change cycle (§ 7): no exploitation reported, but the 2026-08/2026-09 advisories (cache-poisoning / DNSSEC-bypass class) matter for EU/CH government DNS resolvers — upgrade Recursor to 5.2.11 / 5.3.8 / 5.4.3 and DNSdist to 1.9.15 / 2.0.7.
- Tune identity and endpoint detections from § 3 research: add hunts for
rrweb/BitM relay indicators against M365/Entra logins (Bluekit), .NET.configfiles written next to signed PEs (AppDomainManager injection / TinyRCT), COM-based scheduled-task / BITS / WMI activity from unexpected processes (Talos), and review browser-extension governance for<all_urls>extensions (BadBlocker).
7. Verification Notes
- Items dropped — already covered (PD-8):
- Ubiquiti UniFi OS triple-CVE chain (CVE-2026-34908 / -34909 / -34910) — was the full deep dive on 2026-06-24 (including the CISA KEV listing, in-the-wild exploitation and the pre-auth-to-root chain). S1 surfaced it again with no material new delta; not re-reported.
- Turla STOCKSTAY .NET backdoor (Google GTIG, 2026-06-25) — S1 returned the same GTIG primary that was the 2026-06-27 deep dive; no new development, dropped.
- Miasma / "Mini Shai-Hulud" npm worm (LeoPlatform/RStreams wave) — covered as a § 4 UPDATE on 2026-06-27; S3 returned the same Socket.dev analysis with no fresh delta, dropped.
- Vulnerabilities assessed but below the § 2 inclusion bar:
- GitLab CE/EE 19.1.1 / 19.0.3 / 18.11.6 incl. CVE-2026-10712 (Web IDE XSS, CVSS 8.0) — already assessed-and-dropped in the 2026-06-26 and 2026-06-27 briefs (stored XSS, not RCE, no exploitation, below the CVSS-9 gate). Self-managed CH/EU public-sector instances should still update on the normal change cycle (NCSC-NL NCSC-2026-0211).
- PowerDNS Recursor advisory 2026-08 / DNSdist 2026-09 (DNS cache-poisoning / DNSSEC-bypass class, max CVSS 7.5) — no exploitation, no PoC, below the § 2 gate; carried as a normal-cycle patch in § 6 given its relevance to EU/CH government DNS resolvers (PowerDNS, 2026-06-25; BSI WID-SEC-2026-2091).
- Items dropped — outside the recency window (PD-7;
window_hours=36, developing 72 h):- Tata Electronics / World Leaks (Hunters International rebrand) 630 GB leak — primary disclosure 2026-06-24 (~96 h), no fresh in-window development; rolled forward.
- KDDI shared email-platform breach (up to 14.22 M mailbox credentials) — primary 2026-06-24 (~96 h); APAC nexus; the multi-tenant shared-platform lesson noted for a future weekly. Rolled forward.
- River Financial Corp SEC 8-K ransomware disclosure — filing 2026-06-25,
[SINGLE-SOURCE](SEC 8-K/StockTitan only), low CH/EU relevance; rolled forward.
- Items dropped — relevance / novelty:
- SANS ISC "Terrabot" IoT botnet (Mirai/Gafgyt variant exploiting decade-old D-Link / GPON / MVPower flaws)
[SINGLE-SOURCE]— pedagogically useful but the campaign exploits ~2016–2018-era vulnerabilities with no new development; dropped to keep signal density.
- SANS ISC "Terrabot" IoT botnet (Mirai/Gafgyt variant exploiting decade-old D-Link / GPON / MVPower flaws)
- Reduced-confidence / attribution items: the Jaguar Land Rover Russian attribution (§ 1) is MEDIUM confidence — sourced to a New York Times investigation relayed via TechCrunch / The Next Web, not an official UK government attribution or a CERT advisory. Reported as the investigators' claim per the fake-news guard.
- Single-source (primary research) items: the Cisco Talos COM-abuse primer (§ 3) is single-source by nature (the lab's own research); included under the primary-research carve-out.
- Contradictions: the Keycloak fixed-version reporting differed across sub-agents (official Keycloak release notes name 26.6.4, 2026-06-26; BSI/GitHub references also cite 26.4.x / 26.6.x backport branches). The brief cites the official Keycloak release-notes version (26.6.4) as authoritative and points Red Hat Build of Keycloak users to the matching RHSA errata.
- Verification remediation (Phase 5.7): an iteration-3 truth finding removed an unsupported claim from the JLR item — the cited TechCrunch / The Next Web articles do not carry the "UK Cyber Monitoring Centre Category-3 systemic event / surpassing WannaCry" wording (and the Evidence quote attributed to The Next Web was not in the source). The supported facts are retained: the investigators'/NYT Russian-attribution framing, the ~six-week production halt, ~£1.9 bn / $2.5 bn economic impact, and 5,000+ affected suppliers. Earlier iterations corrected NAIC granular file counts, the PowerDNS CVE id, the missing PeopleSoft CVE (CVE-2026-35273), and the Bluekit/Varonis source URL and date.
- Sub-agents: all four research sub-agents (S1–S4, Claude Sonnet 4.6) returned within the window (250–665 s).
- Source-health probe:
tools/source_health.pydid not complete within this run's time budget (full 150-source sweep); the prior snapshot (2026-06-27) is retained and the weekly GitHub Action re-probes. No per-source accessibility action derived this run. - Coverage gaps: ncsc-ch-security-hub (Week 26 Wochenrückblick HTTP 404 — not yet published; no in-window NCSC-CH post); cert-eu (latest advisory 2026-06-10, out of window); cert-fr / anssi-fr (avis latest 2026-06-18, feed otherwise stale with 2025 items); databreaches-net (per-article drill-down 403 for a fourth consecutive run — transport block, not demoted; the RSS feed served and the stories reached the brief via primary pivots); mandiant-gtig (Feedburner stale/empty — direct article fetch used); sophos-xops (feed 404, no in-window research); dfirreport (feed accessible but all items older than 72 h).