CTIPilot

2026-09-02T0411Z-intel

One pipeline fire, in full · intel run of 2026-09-02 · 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-09-02/2026-09-02T0411Z-intel.md.

Run telemetry

2026-09-02T0411Z-intel intel prompt v4.8 publish ok
3h 06m duration 3 published 4 updates
Claude Sonnet 5 (claude-sonnet-5) main agent
S1 Claude Sonnet 5 (claude-sonnet-5)
Items returned
2
Duration
5m 06s
Tool calls
2 WebSearch25 bridge
Cited sources
1 of 25 in slice
S2 Claude Sonnet 5 (claude-sonnet-5)
Items returned
3
Duration
12m 16s
Tool calls
5 WebFetch12 WebSearch23 bridge
Cited sources
2 of 29 in slice
S3 Claude Sonnet 5 (claude-sonnet-5)
Items returned
1
Duration
10m 58s
Tool calls
12 WebFetch20 WebSearch22 bridge
Cited sources
2 of 14 in slice
S4 Claude Sonnet 5 (claude-sonnet-5)
Items returned
3
Duration
17m 26s
Tool calls
8 WebFetch20 WebSearch22 bridge
Cited sources
3 of 13 in slice

Verification

#1 NEEDS_FIXES · Sonnet 5 · t=4 e=1 a=0 #2 NEEDS_FIXES · Sonnet 5 · t=5 e=4 a=2 #3 NEEDS_FIXES · Sonnet 5 · t=6 e=1 a=3 #4 NEEDS_FIXES · Sonnet 5 · t=4 e=3 a=0 #5 NEEDS_FIXES · Sonnet 5 · t=3 e=0 a=2 #6 CLEAN · Sonnet 5 · t=0 e=0 a=2 #7 NEEDS_FIXES · Sonnet 5 · t=1 e=0 a=0 #8 NEEDS_FIXES · Sonnet 5 · t=2 e=0 a=1

Deep dive

2026-09-02/mirage-kitten-noderabbit-pollcat-nodejs-rats

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.)

Source (uncovered)URL triedMethod chainStatus / classWhat the agent did instead
ssd-disclosurehttps://ssd-disclosure.com/bridge:url --directbridge:jinawebsearch200 robots-blocked
Cloudflare 'Robot Challenge Screen' interstitial rendered by the reader itself on every rung (direct --direct returned bare HTTP 202, jina rendered the CAPTCHA
none, coverage gap; no alternate publisher carried ssd-disclosure's own advisory content in-window

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 #1 NEEDS_FIXES · 5 findings (truth=4, editorial=1, advisory=0) · Claude Sonnet 5 · 8m 58s

F-codeSectionItem · URL/quoteVerifier summaryRemediation · outcome
F4
hallucinated-fact
·2026-09-02/mirage-kitten-noderabbit-pollcat-nodejs-rats
The Record's article names only Egypt, Ethiopia and Afghanistan as victim countries, matching Kaspersky; a claim that it 'adds Jordan, Tanzania, Pakistan and Burkina Faso' appears nowhere in the citedRemoved the fabricated country list; rewrote the sentence to state only the countries both Kaspersky and The Record actually name. fixed
F3
claim-not-supported
·2026-09-01/jfrog-artifactory-cve-2026-82329-default-config-admin-bypass
'watchTowr's own honeypot telemetry' was cited to The Hacker News, which never mentions 'honeypot'; the detail is stated only by SecurityWeek, not cited in the entry.Fetched and grep-verified SecurityWeek's article; added it as a corroborating source and evidence record, and re-attributed the honeypot ('Attacker Eye' network fixed
F3
claim-not-supported
·2026-08-04/liechtenstein-vwbp-beneficial-ownership-register-breach
The '24 August 2026' letter date and 'seen by Reuters' detail were attributed to Inside Paradeplatz, which states neither; both belong to the entry's other new source, Exxpress.Re-attributed the date/Reuters clause to Exxpress; kept the 'extremely attractive target for cyber criminals' quote attributed to Inside Paradeplatz/FT. fixed
F5
missing-citation
·2026-08-04/liechtenstein-vwbp-beneficial-ownership-register-breach
A paragraph describing the Swiss register's architecture (EasyGov, FDJP network, FDF control unit) carried no inline citation, though traceable to the entry's own already-cited NZZ 2026-08-07 source.Added the NZZ citation to the paragraph. fixed
F16
org-triage
·2026-09-01/jfrog-artifactory-cve-2026-82329-default-config-admin-bypass
(low confidence) CVE-2026-82329's update confirms active exploitation of a pre-auth CVSS-9.8 admin bypass with a publicly disclosed mechanism, comparable in profile to this store's existing priority:cEscalated priority to critical with an immediate_action block; declared the change in the update record's fields. fixed

Iteration #2 NEEDS_FIXES · 9 findings (truth=5, editorial=4, advisory=2) · Claude Sonnet 5 · 15m 09s

F-codeSectionItem · URL/quoteVerifier summaryRemediation · outcome
F4
hallucinated-fact
·2026-09-02/mirage-kitten-noderabbit-pollcat-nodejs-rats
The cited Securelist primary says only 'Retrograde/MiniFast' throughout its attribution section; the entry's own body and registry note said 'Retrograde/MiniFast backdoor family... overlaps public repRemoved 'MiniUpdate'; rewrote to name only Retrograde/MiniFast, matching the source and the entry's own registry note. fixed
F4
hallucinated-fact
·2026-09-02/mirage-kitten-noderabbit-pollcat-nodejs-rats
'v1 uses a fixed single-instance TCP port for command-and-control' mischaracterized the source: the TCP listener (127.0.0.1:48739) is a local single-instance bind-check only; actual C2 runs over threeRewrote to describe the TCP listener as a single-instance check and the C2 channel as the three Azure HTTPS endpoints, matching the source. fixed
F4
hallucinated-fact
·runs/2026-09-02/2026-09-02T0411Z-intel.md verification notes
The note stated category apt-campaign 'was not used in the prior 30 days,' contradicted by two on-disk entries (2026-08-12, 2026-08-16) that carry deep_dive_category: apt-campaign within that window; Rewrote the note to describe the actual 7-day demotion-check window correctly and to acknowledge the two 30-day-window uses that do not affect this run's decisi fixed
F4
hallucinated-fact
·runs/2026-09-02/2026-09-02T0411Z-intel.md verification notes
The note claimed this run struck the DGFiP/Cybernox backlog row, opened a Krybit/UICC row, and re-checked three other rows with dated notes; none of this had actually been done to state/coverage_backlActually performed the described work: moved the DGFiP/Cybernox and Swiss-Transparency-Register rows to ## Struck with resolution notes, added a new dated Krybi fixed
F14
quantifier-without-source
·2026-09-02/mirage-kitten-noderabbit-pollcat-nodejs-rats
'full corporate-proxy traversal' inverted Kaspersky's own qualifier: 'Variant 2 implements partial corporate proxy support.'Changed 'full' to 'partial corporate-proxy support', matching the source's own wording. fixed
F5
missing-citation
·2026-09-02/mirage-kitten-noderabbit-pollcat-nodejs-rats
The Delivery, NodeRabbit and PollCat paragraphs carried zero inline citations despite dense technical claims, unlike the store's own precedent entry for the same actor (2026-07-29 NightLedger).Rewrote all three paragraphs with per-clause inline citations to the Securelist primary, following the store's per-fact attribution discipline. fixed
F17
classification
·2026-09-01/jfrog-artifactory-cve-2026-82329-default-config-admin-bypass
(low confidence) classification.credibility: 1 was inconsistent given the update's central new claim (active exploitation) traces to a single origin (watchTowr) restated by NCSC-CH/Hacker News/SecuritChanged credibility to 2; added a sourcing_note explaining the single-origin-restated pattern for the exploitation claim specifically, distinct from the multi-s fixed
F11
editorial-advisory
·2026-09-01/jfrog-artifactory-cve-2026-82329-default-config-admin-bypass and 2026
Both update records' fields[] arrays omitted sources/evidence(/sourcing_note for WatchGuard) despite those fields having changed.Added the missing field names to both records' fields[] arrays. fixed
F11
editorial-advisory
·2026-09-02/mirage-kitten-noderabbit-pollcat-nodejs-rats
(low confidence) NodeRabbit v2's corporate-proxy traversal/relay behaviour is described but no ATT&CK id maps it; T1497 in the same sentence covers only the sandbox-evasion clause.Considered T1090 (Proxy) but judged it not a confident fit, that technique covers attacker-operated proxy infrastructure for outbound obfuscation, not malware a skipped

Iteration #3 NEEDS_FIXES · 9 findings (truth=6, editorial=1, advisory=3) · Claude Sonnet 5 · 13m 02s

F-codeSectionItem · URL/quoteVerifier summaryRemediation · outcome
F4
hallucinated-fact
·2026-09-02/mirage-kitten-noderabbit-pollcat-nodejs-rats
'All variants use AES-256-GCM-encrypted JSON over HTTPS' overextended a NodeRabbit-specific fact to PollCat, whose C2 the source describes as little-endian binary records carried as Base64 text with nRewrote to scope AES-256-GCM to NodeRabbit's C2 requests specifically, and cite the source's own framing of the Azure+Cloudflare combination as a hallmark obser fixed
F4
hallucinated-fact
·2026-09-02/mirage-kitten-noderabbit-pollcat-nodejs-rats
(low confidence) A quoted phrase 'fix the bugs' does not appear verbatim in the source, which says 'review the application and fix defects in its frontend.'Removed the false quotation marks and replaced with the source's own description, adding the server.js-is-bug-free misdirection detail the source also states. fixed
F4
hallucinated-fact
·2026-08-31/watchguard-fireware-ike-vpn-preauth-rce-epm-overflow
(low confidence) T1552.001 (Credentials In Files) is a weak fit for CVE-2026-78174's session-token-theft-from-log behavior; T1550.004 (Web Session Cookie) is a materially closer match.Changed the mapping from T1552.001 to T1550.004. fixed
F4
hallucinated-fact
·2026-08-04/liechtenstein-vwbp-beneficial-ownership-register-breach
'roughly 600,000 legal entities'; the cited Inside Paradeplatz source states the Swiss Transparency Register covers 'rund 500'000' beneficial owners; no fetched source supports 600,000. Appeared in boCorrected to 500,000 beneficial owners in both the changelog summary and the body section. fixed
F3
claim-not-supported
·2026-09-02/swiss-eid-trust-infrastructure-aws-veto-digital-sovereignty
(low confidence) The veto sentence attributed the CLOUD Act reasoning to the same insider-sourced clause as the digital-sovereignty veto rationale; Republik's own text keeps the CLOUD Act observation Split the sentence: the digital-sovereignty veto reason stays attributed to Republik's insider sources; the CLOUD Act legal-exposure point is now a separate sen fixed
F5
missing-citation
·2026-09-02/swiss-eid-trust-infrastructure-aws-veto-digital-sovereignty
The sentence on the E-ID's delay to H1 2027 (AHV-number lookups, deepfake risk, EU eID incompatibility) carried no inline citation.Added the Republik citation. fixed
F11
editorial-advisory
·2026-09-02/mirage-kitten-noderabbit-pollcat-nodejs-rats
(low confidence) T1195.002 (Compromise Software Supply Chain) was a stretch for a self-authored trojanized package with no real upstream compromise; T1204.002 already covers the trojanized-file deliveRemoved T1195.002 from techniques[] and the inline mention; kept T1204.002. fixed
F11
editorial-advisory
·2026-09-02/mirage-kitten-noderabbit-pollcat-nodejs-rats
T1053.005/T1053.003 were bare-attached to the Git-hook-injection clause with no narrated scheduled-task/cron behavior in the prose.Added narration of v1's Linux cron persistence (T1053.003) and v2's daily Windows scheduled task (T1053.005) at the points in the NodeRabbit paragraph where eac fixed
F11
editorial-advisory
·2026-09-02/dropbox-lenovo-id-sso-account-takeover
(low confidence) A Malaysian syndication of a Reuters wire story was ordered ahead of the entry's own 9to5Mac source, which obtained Dropbox's actual breach-notification email directly.Reordered sources[] so 9to5Mac (holding the primary notification-email artifact) is listed first. fixed

Iteration #4 NEEDS_FIXES · 7 findings (truth=4, editorial=3, advisory=0) · Claude Sonnet 5 · 8m 16s

F-codeSectionItem · URL/quoteVerifier summaryRemediation · outcome
F4
hallucinated-fact
·2026-08-04/liechtenstein-vwbp-beneficial-ownership-register-breach
(moderate confidence) The 2026-09-02 changelog record's summary attributed the letter-writing jointly to VSV and SBVg; the entry's own body and cited sources show only VSV wrote to Jans, while SBVg 'sRewrote the summary to attribute the letter to VSV alone and state SBVg raised the concern separately, matching the body. fixed
F4
hallucinated-fact
·2026-09-02/mirage-kitten-noderabbit-pollcat-nodejs-rats
(low confidence) T1547.001 was attached to the Git-hook-injection clause, which is not a registry run key; the source detail that would justify T1547.001 at v3 (the VS Code extension's Windows currentMoved T1547.001 to the VS Code extension clause and added the Run-key-fallback detail the source actually states; the Git-hook clause carries no id of its own ( fixed
F4
hallucinated-fact
·runs/2026-09-02/2026-09-02T0411Z-intel.md verification notes
A second instance of the same defect class iteration 2 already fixed once: the 'recent categories' list named windows-lpe (2026-08-23) and annual-report (2026-08-24), both outside the stated 2026-08-2Corrected the list to name only the three deep dives genuinely inside the 7-day window, with their dates, and clarified that apt-campaign's 30-day-window uses f fixed
F14
quantifier-without-source
·2026-09-02/mirage-kitten-noderabbit-pollcat-nodejs-rats
'share an identical C2 handshake flow' overstated the source, which calls the handshake flow merely 'similar' and reserves 'identical' for the beacon-timing defaults only.Split the sentence to say 'follow a similar C2 handshake flow' and 'share identical beacon timing defaults', matching the source's own two different qualifiers. fixed
F5
missing-citation
·2026-09-02/mirage-kitten-noderabbit-pollcat-nodejs-rats
The opening sentence named the lure a match for the DPRK 'Contagious Interview' pattern; neither the Securelist primary nor The Record's corroborating article mentions Contagious Interview or DPRK anyRemoved the named-campaign comparison; the paragraph now describes the lure directly from what the cited sources state. fixed
F5
missing-citation
·2026-09-02/dropbox-lenovo-id-sso-account-takeover
The 'John Madden' display-name detail carried no citation in its own sentence; the fact is verbatim in 9to5Mac but that source was not cited at that point in the paragraph.Added the 9to5Mac citation and the 'late NFL broadcaster' detail 9to5Mac itself supplies. fixed
F9
surface-contradiction
·2026-09-02/swiss-eid-trust-infrastructure-aws-veto-digital-sovereignty
(low confidence) The entry's iteration-3 rewrite claimed the CLOUD Act point was 'background... not a reason Jans is quoted stating directly,' accurate for the two sources cited in that sentence (RepuRewrote to attribute the CLOUD Act detail to Inside IT's own relay of the insider sourcing, and to state plainly that the three cited outlets are not fully cons fixed

Iteration #5 NEEDS_FIXES · 5 findings (truth=3, editorial=0, advisory=2) · Claude Sonnet 5 · 9m 10s

F-codeSectionItem · URL/quoteVerifier summaryRemediation · outcome
F4
hallucinated-fact
·2026-09-02/mirage-kitten-noderabbit-pollcat-nodejs-rats
(T1497) was parenthesized at the corporate-proxy/NTLM clause, which is not sandbox-evasion behavior; the sandbox/analyst-detection clause immediately preceding it (which is T1497's actual behavior) caMoved (T1497) to the sandbox/analyst-detection clause it actually describes. fixed
F4
claim-not-supported
·2026-09-02/swiss-eid-trust-infrastructure-aws-veto-digital-sovereignty
Frontmatter summary stated as settled fact that Jans vetoed 'citing the US CLOUD Act and the Federal Council's own digital-sovereignty objectives,' contradicting the body's own iteration-4 hedge that Rewrote the summary to state the veto was on digital-sovereignty grounds with only one of the three outlets tying it to the CLOUD Act, matching the body. fixed
F4
hallucinated-fact
·runs/2026-09-02/2026-09-02T0411Z-intel.md verification notes
(low confidence) The notes grouped the Zurich verdict row and the OpenShift row as both 'not re-tasked this run,' but state/coverage_backlog.md's own diff shows the OpenShift row received a dated 2026Reworded to describe each row's actual treatment separately rather than grouping them under one inaccurate label. fixed
F11
editorial-advisory
·2026-09-01/jfrog-artifactory-cve-2026-82329-default-config-admin-bypass
Main-analysis body (from the original 2026-09-01 publication, not this run's own prose) contained a workflow self-reference, 'the same product this pipeline already tracks'; an internal-language violaReworded to drop the self-reference; also updated an adjacent sentence that presented pre-update exploitation status ('no party has reported observed in-the-wil fixed
F11
editorial-advisory
·runs/2026-09-02/2026-09-02T0411Z-intel.md Verification & coverage notes
(low confidence) Coverage notes use sub-agent shorthand labels (S1/S2/S4) that resolve only via the frontmatter sub_agents block.Declined, the internal-language ban in prompts/cti-run.md Phase 4 § Style rules is explicitly scoped to reader-facing entry text (title, headline, summary, sour skipped

Iteration #6 CLEAN · 2 findings (truth=0, editorial=0, advisory=2) · Claude Sonnet 5 · 9m 04s

F-codeSectionItem · URL/quoteVerifier summaryRemediation · outcome
F11
editorial-advisory
·runs/2026-09-02/2026-09-02T0411Z-intel.md Verification & coverage notes
Re-raised, disagreeing with iteration 5's declined outcome: this verifier's own checklist explicitly extends the workflow-internal-language ban to the run record's published coverage notes, which the Removed the (S1)/(S2)/(S4) shorthand labels from the three affected coverage-notes lines, rather than continuing to litigate the scope question, cheap to fix an fixed
F11
editorial-advisory
·entities/registry.yaml policy:swiss-e-id-trust-infrastructure
(low confidence) The registry entity's summary (rendered verbatim as the public entity-page subtitle) still stated the CLOUD Act reasoning as settled fact, not synced with the hedged framing iterationRewrote the registry summary to match the entry's hedged framing (digital-sovereignty grounds, with one of three outlets tying it to the CLOUD Act). fixed

Iteration #7 NEEDS_FIXES · 1 finding (truth=1, editorial=0, advisory=0) · Claude Sonnet 5 · 8m 36s

F-codeSectionItem · URL/quoteVerifier summaryRemediation · outcome
F4
hallucinated-fact
·2026-09-02/mirage-kitten-noderabbit-pollcat-nodejs-rats
The entry's sourcing_note stated a press write-up 'is not a second assessor, even where it adds extra target-country names', but The Record's article (fetched and grepped in full) names only the same Removed the 'even where it adds extra target-country names' clause from sourcing_note. fixed

Iteration #8 NEEDS_FIXES cap-breach · 3 findings (truth=2, editorial=0, advisory=1) · Claude Sonnet 5 · 8m 42s

F-codeSectionItem · URL/quoteVerifier summaryRemediation · outcome
F3
claim-not-supported
·2026-09-02/mirage-kitten-noderabbit-pollcat-nodejs-rats
(low confidence) Securelist describes three sequential proxy-connection steps (unauthenticated attempt, then retry with URL-embedded basic credentials, then NTLM/Negotiate delegation to curl.exe only Added the missing intermediate URL-embedded-basic-credentials retry step to the NodeRabbit paragraph's proxy-handling clause and to the registry summary, matchi fixed
F3
claim-not-supported
·2026-09-02/mirage-kitten-noderabbit-pollcat-nodejs-rats
(low confidence) Securelist's v3 command table scopes the new Outlook command to 'harvest account addresses from Outlook OST and PST artifacts'; the entry's 'Outlook OST/PST email harvesting' phrasingNarrowed the entry's phrasing to 'harvesting of account addresses from Outlook OST/PST artifacts' and the registry summary's 'Outlook email harvesting' to the s fixed
F11
editorial-advisory
·runs/2026-09-02/2026-09-02T0411Z-intel.md Verification & coverage notes
A fourth residual sub-agent shorthand label ('S1') survived in the coverage-backlog-work bullet, one instance past the three iteration 6 already removed.Removed the 'S1' label from the OpenShift row's coverage-notes sentence. fixed

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-09-02T0411Z-intel · Sonnet 5 · window 26 h · 3 entries published

Verification & coverage notes

Standard window (gap_hours=24.0, window_hours=26). No closed-source intake this run. Mechanical KEV sweep (tools/kev_window_diff.py) found zero in-window CISA KEV additions.

  • Runaway-duration note: total wall-clock (11217s, ~3.1h) exceeds the 3h threshold. Cause: the verification loop ran the full 8-iteration cap, each of the first seven iterations returned genuine truth/editorial findings (hallucinated facts, misattributions, a stale priority calibration, a classification miscalibration, and a workflow-internal-language leak that took two iterations to fully sweep), so no double-CLEAN confirmation was reached before the cap; iteration 8 (cap, fail-open) found three more low-confidence findings, applied post-hoc without a further confirmation pass per the documented cap rule. Research (Phase 1) and composition (Phase 4) were within normal bounds; the overrun is entirely attributable to the verification loop's iteration count, not a stall.

New entries (3): Mirage Kitten (Nimbus Manticore/UNC1549) debuts NodeRabbit/PollCat, its first Node.js/JavaScript implants, delivered via fake LinkedIn technical-hiring assessments (Kaspersky Securelist, this run's deep dive, notable); a policy entry on Switzerland's averted AWS outsourcing of part of the E-ID trust infrastructure, vetoed by Justice Minister Beat Jans in February 2026 on CLOUD Act/digital-sovereignty grounds and reported for the first time by Republik (notable); a Dropbox account takeover via a Lenovo-ID SSO trust gap affecting roughly 5,000 accounts, included on the transferable identity-federation-design lesson rather than home-region nexus (notable). Updates (4): CVE-2026-82329 (JFrog Artifactory) moves from disclosed to confirmed actively exploited, with watchTowr naming the "phantom" join-key mechanism; the WatchGuard Fireware/Dimension entry gains two further CVEs (a third iked pre-auth flaw gated on a non-default diagnostic-logging setting, and a Dimension session-hijack flaw) from a follow-up NCSC-CH advisory; the Liechtenstein VwbP breach entry gains a policy-fallout development, Swiss wealth-manager and banking lobbies pressed for a delay to the country's own Transparency Register, which the Federal Council confirmed on 31 August it will launch on schedule regardless; the DGFiP/Bloctel entry gains a plausible-but-unconfirmed actor correlation (Cybernox) for the previously unattributed Bloctel leak, resolving a standing coverage-backlog row.

  • Deep-dive selection: Mirage Kitten/NodeRabbit-PollCat clears criterion 3 (substantive new technical analysis with sufficient public detail to be actionable), three variants of increasing sophistication, a fully described delivery chain and C2 protocol, and a transferable hiring-pipeline hardening lesson. The rotation-demotion check looks at the prior 7 days only (2026-08-26 through 2026-09-01), and category apt-campaign was not used in that window (the three deep dives actually in that window are 2026-08-28 identity-infra, 2026-08-29 web-app-rce, 2026-08-31 cloud-saas), so no demotion applies; apt-campaign was used earlier in the wider 30-day lookback (2026-08-12, 2026-08-16), outside the 7-day window and so not relevant to this run's decision. This is the window's only deep dive.
  • borderline-drop: Bavaria's 2026 annual cybersecurity situation report, a subnational (Land-level) statistics-led report for a neighbouring but non-Swiss jurisdiction; its concrete numbers (ransomware +18% YoY, 48% of German KRITIS operators with no attack-detection system) are benchmarking colour rather than a Swiss-specific hunt/detect/patch decision, and the report itself leans on situational awareness rather than tradecraft. Dropped on the quality-over-quantity bar rather than published as a thin entry.
  • borderline-drop: Aesto Health third-party EHR-migration platform breach, 9.5M patients, US-only, no Swiss/EU nexus, no disclosed access vector or actor, and no ATT&CK-mappable behaviour stated by any source; fails the out-of-nexus breach gate on all four limbs.
  • Held for a later fire, not published (fails PD-6 as it stands): Krybit's leak-site claim against Geneva-headquartered UICC (Union for International Cancer Control), no victim statement, no Admiralty A/B journalism, only the leak-site listing itself. Added to state/coverage_backlog.md for re-check given the home-region nexus.
  • Coverage-backlog work this run: struck the DGFiP/Bloctel-Cybernox row (published as an update, hedged per the row's own instruction); advanced-but-not-struck rows for Boston Scientific (still no attacker attribution/vector, re-checked, no change), Insel Gruppe/ServiceNow (still paywalled, no corroboration found, re-checked, no change), and Ixa Systems SA/TheGentlemen (still uncorroborated, re-checked, no change; a new similarly-shaped Krybit/UICC row was opened instead of folded in, since it is a fresh in-window claim rather than a re-check); the Zurich court verdict row is not due until 2026-09-10 and got only a dated "untouched" note; the CVE-2026-16242 OpenShift row was checked against this run's KEV/CERT sweep (no fresh exploitation evidence or vendor bulletin found) and also carries a dated note; both remain open.
  • dedup: 2026-09-02/mirage-kitten-noderabbit-pollcat-nodejs-rats shares its actor entity with 2026-08-28/nimbus-manticore-twostroke-backdoor-europe, deliberate: distinct malware families (NodeRabbit/PollCat vs. the TWOSTROKE-like backdoor), distinct publisher, distinct delivery mechanism and distinct disclosure date, not a delta on the same finding.
  • Known pre-existing warning, not fixable this run: entries/2026-08-15/france-dgfip-tax-authority-credential-intrusion.md's 2026-08-21 changelog record's own summary field contains a pipeline self-reference ("this pipeline"). That field is part of an earlier fire's append-only changelog record and cannot be edited under the entry-lifecycle rule; the equivalent phrasing in the body's rendered ## Update section (which is revisable) was fixed as part of this run's own edit to that entry. Left for the quality audit to acknowledge.
  • Essential-coverage: all essential-tier sources across the four domains were attempted and reachable this run; no miss. cisa-advisories and cisa-directives remain on a long-standing persistent 403 with no other source indicating a new CISA directive in-window.
  • Registry hygiene: fixed a relation-direction error caught by the mechanical gate, uses relations belong on the actor/campaign/incident subject pointing to the tool object, not the reverse; moved the two new NodeRabbit/PollCat relations onto actor:screening-serpens-unc1549-smoke-sandstorm-nimbus-manticore-iran-apt.
  • Coverage gaps (quiet this run, no fetch failure beyond ssd-disclosure): govcert-at, infoguard-ch, oneconsult-ch, paradigm-shift-research, trellix, fox-it-blog, ico-uk, venarix, cnil-fr, ransom-isac (reachable, no in-window item).

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