2026-06-29-6d39189a

• Quiet window. Gap to prior brief is 24 h (standard daily; window_hours = 36, developing_window_hours = 72). EU/CH and CISA-KEV/national-CERT signal was genuinely thin: no new KEV additions, and all CERT-EU / CERT-FR / NCSC-NL / BSI advisories predate the window. Three items cleared the bar; the brief is short by design, not by omission.
• Items dropped (relevance / nexus): AssuranceAmerica Managing General Agency breach (>1.1 M US insurance customers, 7 states; databreaches.net / PRNewswire, disclosed 2026-06-28) — in-window disclosure but a months-old (March 2026) US-domestic incident with no CH/EU nexus and no new technique beyond single-employee credential compromise → bulk exfiltration; logged here rather than carried.
• Items dropped (recency / already covered): StrikeShark / SharkLoader Chinese-nexus Cobalt Strike loader (Kaspersky Securelist 2026-06-24, The Hacker News 2026-06-26) — both primary and corroborating sources fall outside the strict 36 h window; surfaced by S1 as contextual only and excluded.
• Recency note (§ 3 included with annotation): the 0DIN AI-coding-agent item's in-window coverage is the BleepingComputer article timestamped 2026-06-27 14:22 UTC, which sits ~1.7 h before the strict 36 h cutoff (2026-06-27 16:23 UTC) but within the 72 h developing window; the underlying 0DIN research is 2026-06-25. Included as a substantive novel-technique research item with dates stated plainly; not presented as breaking-today.
• Reduced confidence — aggregator-only sourcing (§ 1): the KDDI breach is carried on three news outlets (BleepingComputer, SecurityAffairs, Infosecurity Magazine) with no reachable vendor/regulator primary — KDDI's own English disclosure was not located and the Japanese corporate announcement sits behind a paywall (japantimes, HTTP 402). The three outlets corroborate each other on the core facts (six ISPs, ~14.22 M worst-case figure, third-party platform vector); treat the precise figure as KDDI's stated worst case.
• Reduced confidence / single substantive source (§ 4): the scope and attribution claims for the Gogs/K8s campaign (thousands of hosts, 300+ nodes, "Realm C2", actor "Unknown") rest on the Wiz Threat Research tracker entry as the only substantive source; Rapid7 corroborates the Gogs CVE mechanics but not the campaign link. The CVE itself and the patch are independently established (covered 2026-06-20). Treat campaign-scale figures as Wiz's assessment.
• Contradictions: none unresolved this run.
• Tooling note: the end-of-run tools/source_health.py accessibility probe exceeded its 6-minute budget and was terminated before writing a fresh state/source_health.json; the existing snapshot (generated 2026-06-28 by the weekly GitHub Action) is retained unchanged. No source-health actions were derived this run; the next probe will refresh it.
• Sub-agents: S1–S4 all returned within the 30-min cap (all Claude Sonnet 4.6). S2 (Switzerland/Europe/public sector) returned zero qualifying in-window items after checking NCSC-CH, CERT-EU, CERT-FR, BSI, NCSC-NL, ENISA EUVD, CERT.at and CERT.pl — none had in-window publications.
• Coverage gaps: ncsc-ch-security-hub (Week 26 review not yet published; expected 2026-06-30); cert-eu (latest advisory 2026-06-10, outside window); cert-fr (latest 2026-06-19); ncsc-nl (latest 2026-06-25); bsi-de (latest WID-SEC 2026-06-25/26); enisa-euvd (no in-window exploited/critical entries); cert-at, cert-pl (Poland SIM-swap arrests ~46 h before window); cisa-kev (no additions in window); databreaches-net (article-level HTTP 403 via bridge; feed accessible, used feed summaries); sec-edgar (0 material cyber 8-K hits in window); ico-uk, cnil, edpb (no in-window enforcement); mandiant-gtig (feed returned empty); dfirreport, red-canary, check-point-research (no in-window primary posts).

Unmatched action items (migrated)

• Hunt your Kubernetes estate for the campaign's post-access behaviour (§ 4): K8s API-server audit-log create on workflows.argoproj.io and on pods from unexpected service accounts, privileged-container escapes, and unexplained miner-class CPU/GPU load. Enforce Pod Security Admission restricted and strip node-escalation rights from default service accounts.
• Add AI-coding-agent abuse to your detection backlog (§ 3): alert on DNS TXT-record queries from developer-tooling process trees (node/python/pip/npx) during repo setup and on agent processes spawning unexpected shell children; require human-in-the-loop for external network calls in agent-executed init scripts. No patch exists — this is a behavioural/control change.
• Treat the KDDI leak as a credential-stuffing precursor (§ 1): monitor external-facing authentication for anomalous logins from Japanese-ISP email address spaces, and audit third-party vendor access to your own subscriber/identity-management platforms with MFA enforced on the administration plane.

Migrated from briefs/2026-06-29.md (v2).