Shai-Hulud made publishing credentials part of the infection
The first Shai-Hulud wave linked dependency installation to secret theft and further package publication.
Security cases organised by event year. Open a case for the technical account, response lessons and source documents.
The first Shai-Hulud wave linked dependency installation to secret theft and further package publication.
A GitHub MCP demonstration shows how untrusted issue text can be promoted into unintended tool use.
The March 2025 compromise connected mutable action tags, secret-bearing logs and credentials that could outlive the malicious code.
The July 2024 content-update failure made boot paths, recovery access and correlated dependencies part of the security conversation.
A pre-authentication race condition showed why SSH keys, package backports and server patch state belong in separate checks.
A third-party script can change a trusted page. The polyfill.io case makes that delegation explicit.
A repair prompt can be a malware-delivery step. Investigate the requested action and whether it actually ran.
The 2024 Snowflake customer-account campaign followed stolen identities into database access and data export.
The 2024 disclosure put release archives, generated build files and distribution-specific build conditions inside the trust boundary.
The 2024 response shows why transaction state and temporary recovery routes belong in continuity planning.
The February 2024 ScreenConnect flaws put server ownership, administrative reach and tenant boundaries in the response scope.
CVE-2023-44487 made request churn and protocol termination more useful questions than a connection count alone.
CVE-2023-4966 linked a memory-disclosure flaw to reusable sessions that needed a separate recovery decision.
CVE-2023-4863 required inventory of browsers, embedded renderers and image-processing workers.
The 2023 campaign separated two jobs that incident tickets often collapse: closing the vulnerability and investigating earlier access.
The 3CX investigation traced a compromised software input into another vendor’s release environment.
The recovery task follows the stolen session into the mailbox, its persistence settings and the business conversations it exposed.
Assess CVE-2022-22965 using the actual runtime, Spring dependencies, packaging and servlet container.
A retrospective on embedded Java dependencies, incomplete early fixes and the evidence needed to close a remediation ticket.
Exchange patch state, earlier exploitation and persistent access need separate evidence in a ProxyLogon response.
SUNBURST made software provenance, management identities and independent recovery part of the same investigation.
The NotPetya record connects a poisoned update, stolen credentials and remote administration across recovery boundaries.
WannaCry, MS17-010 and the gap between a patch notice, installed software and a service that can recover.