The first 30 minutes establish control; remediation continues tonight.
0–10 minutes — contain and preserve. N-central first: remove internet access, suspend automation and agent-push jobs, and preserve VM snapshots, databases, audit/job logs, and memory where feasible. Cisco FMC: restrict management access to the IR jump host and capture configuration, audit, process, shell, and network telemetry. CrushFTP: restrict to trusted IPs/VPN and preserve access logs, session stores, configuration, and user changes. Chrome: enforce version 157.0.8103.50 and restart; isolate only endpoints showing exploit or suspicious child-process activity. Cursor: block Claude Code 2.1.312/2.1.313, preserve packages, and classify devices separately as received, installed, executed, or potentially credential-exposed. BO Team: quarantine releases from the affected window; the developer should freeze publishing and disable—but not destroy—the signing key. ARTEX: start an identity/cloud hunt, not estate-wide containment, unless internal indicators appear.
10–20 minutes — remediate against evidence thresholds. No validated N-central or CrushFTP fixed version is established in the evidence here, so keep them isolated until the vendors confirm the correct build. Rebuild N-central if unauthorized jobs, agent commands, privileged access, persistence, or material logging gaps appear; otherwise stage the confirmed update before production. Patch FMC after evidence capture, but rebuild it from trusted media if root access, persistence, configuration tampering, or uncertain integrity is found. Invalidate CrushFTP administrative sessions immediately; rebuild if tooling created users, persistence, or unexplained file/configuration changes. Remove the Cursor extension everywhere, but rebuild only executed systems where persistence, payload execution, or integrity loss is demonstrated. For BO Team, rebuild CI/signing infrastructure cleanly and reconcile source commits, dependencies, build outputs, release hashes, and signing logs before resuming releases.
20–30 minutes — rotate and verify. Rotate N-central service, API, administrator, and downstream credentials from a clean host only after containment, scoped to evidence of access; independently review fleet-wide commands. Rotate FMC/API and managed-device secrets where root or configuration access is confirmed. Rotate CrushFTP administrator or exposed user credentials based on session/file evidence. For Cursor, rotate only secrets accessible to the malicious process after confirmed execution—receipt or installation alone does not prove exposure. Revoke and replace BO Team signing certificates if unauthorized key use or key confidentiality cannot be disproved. Keep three claims at monitoring-only status: ARTEX’s distinct AI capability gain, malicious downstream BO Team releases, and host-level Chrome compromise without sandbox escape or follow-on execution.