ctipilot.ch

2026-07-19T2310Z-weekly

One pipeline fire, in full · weekly run of 2026-07-19 · sub-agent allocation and telemetry, per-iteration verification verdicts and findings, source-list edits, coverage gaps, bridge invocations — and the run's own verification & coverage notes: what was published, what was dropped at the borderline or judged not relevant (and why), single-source carve-outs, and contradictions. Rendered from runs/2026-07-19/2026-07-19T2310Z-weekly.md.

Run telemetry

2026-07-19T2310Z-weekly weekly prompt v3.28 publish ok
41m 02s duration 14 published 2 updates
Claude Opus 4.8 (claude-opus-4-8) main agent
W1 Claude Sonnet 5 (claude-sonnet-5)
Items returned
2
Duration
10m 14s
Tool calls
20 WebFetch15 WebSearch6 bridge
Cited sources
5 of 18 in slice
W2 Claude Sonnet 5 (claude-sonnet-5)
Items returned
2
Duration
9m 45s
Tool calls
16 WebFetch20 WebSearch5 bridge
Cited sources
5 of 8 in slice

Verification

✓ double-CLEAN · Opus 4.8 + Sonnet 5 #? NEEDS_FIXES · Opus 4.8 · t=4 e=0 a=0 #? NEEDS_FIXES · Sonnet 5 · t=0 e=1 a=0 #? CLEAN · Opus 4.8 · t=0 e=0 a=0 #? CLEAN · Sonnet 5 · t=0 e=0 a=0

Deep dive

Entries published (this run)

Sources changed (this run)

Edits this run made to sources/sources.json · promotions, demotions, new candidates, and fetch-method / category / reliability / url corrections (the run record's sources_changed[]). Paginated; 10 per page.

No source-list edits recorded for this run.

Coverage gaps (this run)

Sources this run's brief needed that returned no usable content via any documented recipe. Bridge-recovered or quiet-day sources do NOT appear here. (Distinct from the independent source-accessibility probe at the foot of this section, which probes all active sources regardless of what any run needed.)

No coverage gaps in this run · every source the brief needed returned usable content via its documented recipe.

Bridge invocations (this run)

2 bridge calls this run · these are successful bridge fetches (separate from "Coverage gaps" above).

2 other
  • fetch_source.py url ×1
  • fetch_source.py ncsc-csh recent ×1

Verification findings · all iterations

Per-iteration finding detail. Each table is one verifier pass · what was flagged, how the main agent remediated it, and the outcome. Walking the tables top-to-bottom shows the verifier's debugging trail across iterations.

Iteration #? NEEDS_FIXES · 4 findings (truth=4, editorial=0, advisory=0) · Claude Opus 4.8 · 9m 32s

F-codeSectionItem · URL/quoteVerifier summaryRemediation · outcome
F4
unsupported-quote
The TfL initial-access narrative (credential purchase from criminal forums; helpdesk vishing → password/2FA reset) was quoted/attributed to the NCA page, which carries none of it. The chain is actuallRe-sourced the strand to The Register (2026-07-16), kept only its verbatim phrase "well-known criminal forums", de-quoted the rest to paraphrase, and swapped th
F4
unsupported-quote
"None exploited a Salesforce flaw" was quoted to the Microsoft blog, whose actual wording is "This activity was not the result of a vulnerability inherent to Salesforce. Rather, the threat actors abusDe-quoted to an accurate paraphrase (none exploited a Salesforce vulnerability; each abused trusted OAuth relationships).
F4
nonverbatim-quote
Both entries quoted "even though the triggering commit was unauthorized" (singular); the Microsoft source reads "commits were unauthorized" (plural).Corrected the quote to the plural verbatim wording in both entries.
F14
quantifier-misattribution
The >40%-of-Q2-attacks figure was attributed to the four 'four-headed monster' groups; the source attributes >40% to the FIVE most prolific Q2 groups.Reworded summary and body to attribute the >40% to the five most prolific groups while keeping GuidePoint's 'four-headed monster' framing for the named four.

Iteration #? NEEDS_FIXES · 1 finding (truth=0, editorial=1, advisory=0) · Claude Sonnet 5 · 2m 58s

F-codeSectionItem · URL/quoteVerifier summaryRemediation · outcome
F2
missing-citation
The Oracle EBS bullet was the only looking-ahead item without an inline citation/references entry, though its fact checked out accurate.Added an inline (Help Net Security, 2026-06-30) citation to the bullet, added that source to sources[], and added the Oracle EBS operational entry to references

Verification & coverage notes

The run record's narrative body, verbatim. This is where the run accounts for its own judgement calls — every borderline drop and judged-not-relevant item with its reason, dedup decisions, single-source items and their carve-outs, contradictions, and per-source coverage gaps — so nothing the run considered disappears silently.

Verification & coverage notesrun record body

2026-07-19T2310Z-weekly · weekly · Claude Opus 4.8 · 14 entries published

Weekly strategic run — 2026-W29 (2026-07-13 – 2026-07-19)

ATT&CK pin freshness

tools/attack_data.py --check: up to date — local v19.1 == upstream latest v19.1. No update required this run. Technique ids composed this run were validated against the pinned dataset; the revoked v19 ids were mapped to their survivors before composition (T1562.001 → T1685 "Disable or Modify Tools"; T1574.002 → T1574.001 "DLL"), so no dead id shipped.

Week in review (Phase 1)

51 operational entries across ISO week 2026-W29 (07-13: 7, 07-14: 14, 07-15: 3, 07-16: 7, 07-17: 8, 07-18: 9, 07-19: 3), 14 high-priority, no critical. Working lists persisted to work/<run-id>/week-review.json. Duplicate-week guard: prior -weekly record (2026-07-12) covered W28; W29 not previously covered — cleared.

Strategic output (14 entries)

  • top-stories (2): internet-facing enterprise software under confirmed exploitation (SonicWall SMA1000/UTA0533, ShareFile SZC, Oracle EBS Payments, on-prem SharePoint/AD FS — patching alone is not remediation where creds/machine keys survive); Russian state-nexus pre-positioning against European CI + first joint EU/UK cyber-sanctions (FSB Centre 16 router hijacking, Turla attribution, Poland grid attribution, IP-camera surveillance of NATO supply routes).
  • multi-day (1): identity intrusions all abused a trusted relationship rather than breaking authentication — ShinyHunters OAuth/Entra-SSO vishing, Proofpoint client_id-spoofing credential oracle, Moodle JWT-signature-non-verification takeover, Scattered Spider helpdesk-vishing court record. Builds on (does not re-list) W28's M365 device-code/ROPC/AiTM convergence.
  • vuln-rollup (1): W29 CVE trajectory (9 exploited/KEV, 2 public-exploit, dense critical-unexploited tail); cves: [] by design.
  • sector-patterns (2): CH/EU public-sector & CI incident cluster (ANCPI Romania, IWB Basel, IFAGE Geneva, Metro Mondego, Wind Tre, EY, Abacus); OT/ICS advisory wave (Rockwell CVSS 10.0, Siemens ROX II, WAGO, KNX KEV).
  • incidents-recap (1): the week's breaches were third-party-mediated (service provider, data-centre host, ITSM platform, CI/CD pipeline).
  • research (3): ClickFix crimeware surge & macOS credential-coercion (Europe top victim); AI as tradecraft accelerant (not inflection) + emoji-in-debug-string hunt technique; state-nexus EDR-blinding tradecraft (HelloNet AFD-IOCTL, GoSerpent dwell time).
  • long-running (2): The Gentlemen (update_of W28 — ReliaQuest Q2 leaderboard reversal + Metro Mondego); npm/developer-ecosystem supply-chain wave (update_of W28 — AsyncAPI trusted-publishing twist + Contagious Interview developer-targeting).
  • policy (1): EU CI-resilience regulatory deadlines (ENISA SME CRA maturity model ahead of the 11 Sept Article 14 clock; Germany KRITIS-Dachgesetz CER-Directive registration window opened 17 July).
  • looking-ahead (1): 2026-W29 outlook — items already in motion.

Priority calibration: high reserved for the genuinely week-defining items (both top-stories, the identity multi-day, the CH/EU incident cluster, the third-party-breach recap, the ClickFix-crimeware research, the vuln-rollup); no critical — no single stop-and-act weekly item this week, bar unchanged.

Verification & coverage notes

  • Weekly dedup (replaces PD-8). Dedup ran against the prior weeklies' strategic entries (W28 2026-07-12, W27 2026-07-05). Two items already consolidated in W28 return only as update_of status entries with a fresh in-window delta: The Gentlemen (update_of weekly-w28-the-gentlemen-status — ReliaQuest Q2 leaderboard reversal + Metro Mondego victim) and the npm supply-chain wave (update_of weekly-w28-npm-supply-chain-wave — AsyncAPI trusted-publishing twist + Contagious Interview). The identity multi-day entry is a NEW entry, not an update_of: W28's M365 convergence covered device-code / ROPC / AiTM auth-flow abuse, whereas this week's material is a distinct OAuth-consent / SSO-vishing / JWT-forgery / helpdesk-process sub-pattern with entirely new disclosures — it references and explicitly builds on the W28 entry without re-summarising it (verifier confirmed it extends, not re-lists).
  • Deliberate synthesis-by-reference (the 30 dedup WARNs). check_run.py emits 30 dedup WARNs of the "confirm the non-update decision was deliberate" class because every strategic entry shares entity keys with the operational entries it synthesises via references. This is the weekly's designed function (re-framing the week's operational signal with a strategic lens), not update-masquerade; each is deliberate and confirmed by all four verifier iterations. These are the documented weekly-polarity WARNs, not fixable defects.
  • Priority calibration. high on both top-stories, the identity multi-day, the CH/EU incident cluster, the third-party-breach recap, the ClickFix-crimeware research and the vuln-rollup — the genuinely week-defining items. No critical: no single stop-and-act weekly item this week (bar unchanged). The AI-accelerant, EDR-blinding, OT/ICS, both long-running, policy and looking-ahead entries are notable.
  • Single-source items (correctly flagged). The state-nexus EDR-blinding research entry is single-source (Kaspersky GReAT for both HelloNet and GoSerpent), reliability B / credibility 2; the GoSerpent–TetrisPhantom link is Kaspersky's own potential, not confirmed, association. The Clop attribution on ShareFile and the DragonForce/IFAGE and ByteToBreach/ANCPI extortion claims are single-analyst/actor claims, attributed as such and not stated as fact.
  • Citation-date discipline (v3.26 F3). Every inline (Publisher, YYYY-MM-DD) uses the source's own publication date taken from the referenced operational entry's sources[] records or the W1/W2 findings, never a discovery/processing date. Verifier iterations 1, 3 and 4 spot-checked this across the quote-bearing entries.
  • Verification. Four iterations (Opus/Sonnet/Opus/Sonnet rotation). Iteration 1 (Opus) found 4 truth defects — all quote/attribution (a TfL narrative mis-cited to the NCA page rather than The Register; a non-verbatim ShinyHunters "None exploited a Salesforce flaw" quote; a singular/plural AsyncAPI quote in two entries; a >40%-of-Q2 figure attributed to four groups vs the source's five) — all remediated. Iteration 2 (Sonnet) confirmed all four fixes and found one minor editorial gap (a looking-ahead bullet missing its inline citation), remediated. Iterations 3 (Opus) and 4 (Sonnet) both returned CLEAN cold — a confirmed double-CLEAN on two different models. No entries dropped.
  • Horizon research. W1 (threat-actor/campaign/research/report) returned 2 items (The Gentlemen Q2 leaderboard delta; Insikt Iran AI playbook → new entities actor:apt42, actor:cyberav3ngers). W2 (strategic/policy) returned 2 items (ENISA SME CRA maturity model; Germany KRITIS-Dachgesetz registration window), the KRITIS fine figures held at MEDIUM confidence pending the Bundesgesetzblatt text. Both sub-agents ran on Sonnet 5 (env-reported; definitions pin research to sonnet).
  • ATT&CK pin. --check up to date (v19.1). Two revoked v19 ids were mapped to survivors before composition (T1562.001 → T1685; T1574.002 → T1574.001); no dead id shipped. ICS-ATT&CK (T0xxx) ids were deliberately NOT used — the pinned dataset is enterprise-attack, so OT entries map only the enterprise vector (T1190).
  • Source health. tools/source_health.py probed 162/162 sources (98 ok, 64 bridge-ok), 0 UNSOLVED flags — no sources.json changes needed (sources_changed: []).
  • Coverage gaps (W1/W2): W1 logged 9 quiet/recycled-news sources (Trellix, CrowdStrike, Shadowserver, Truesec Forest-Blizzard recap, WithSecure GREYVIBE, InfoGuard, Zimperium, CSA Labs, SANS-NewsBites); W2 logged 6 (NCSC-CH focus/CSH no policy content in-window, FINMA no new cyber guidance, BAKOM/OFCOM none, Council of Europe none, DORA none — the 8 July ESRB/ECB frontier-AI warning and the EU NIS2 CJEU referral are both pre-window and were correctly not fabricated as fresh). No essential-coverage guarantee applies to the weekly.
  • Duplicate-week guard: cleared (prior -weekly = 2026-07-12 covered W28; W29 not previously covered).

← Operations dashboard · day page 2026-07-19 · run-record contract: docs/pipeline.md