Malware in @source-row/source-container
Malware discovered in the npm package @source-row/source-container. Systems with this package installed are considered fully compromised and require immediate remediation.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- @source-row/source-container
A malware incident has been identified in the npm package @source-row/source-container, published as GitHub Advisory GHSA-x8p5-jmxq-hp52.\n\nAny computer with this package installed or running should be considered fully compromised. The malware grants outside entities full control of affected systems, allowing potential access to all stored secrets and cryptographic keys.\n\nImmediate remediation requires rotating all secrets and keys from a separate, uncompromised computer. While the package should be removed, complete removal of all malicious artifacts cannot be guaranteed due to the level of system compromise achieved by the malware.\n\nAffected package: @source-row/source-container (npm).
Indicators of compromise
- Packages
- @source-row/source-container
Remediation
- Immediately rotate all secrets, API keys, and cryptographic material from a separate, uncompromised computer
- Remove the @source-row/source-container package from all affected systems
- Conduct a full security audit of any system that had this package installed
- Review system logs and network traffic for signs of unauthorized access or data exfiltration
- Consider full system reimaging if the package was installed on production or sensitive systems
Sources
- GitHub Advisory GHSA-x8p5-jmxq-hp52 · GitHub Advisory Database
Cite this entry
"Malware in @source-row/source-container." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 29, 2026; last updated June 29, 2026. https://supplychainattack.org/incident/malware-in-source-row-source-container-1y3j0y
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- resolvedcritical
Malicious code in github-policy-bot (npm)
The npm package github-policy-bot contained malicious code that exfiltrated host identifiers and environment metadata during installation via a postinstall script. The package name shadowed a legitimate Google-owned repository and was authored under a placeholder account claiming security research purposes.
npmCompromised packageTyposquatting - containedcritical
Malicious code in crypto-javas (npm)
The npm package crypto-javas contains malicious code in its postinstall hook and main entrypoint that harvests environment variables (including CI secrets like AWS_*, GITHUB_TOKEN, NPM_TOKEN) and exfiltrates them to an attacker-controlled backend. The package is presented deceptively as @wizlabs/js-crypto with a placeholder repository.
npmCompromised packageTyposquatting - containedcritical
Malicious code in flydev (npm)
The npm package flydev contains malicious code designed to destroy Windows systems. The package masquerades as a utility but executes destructive operations including filesystem deletion, process termination, memory exhaustion, and fork bombs when invoked.
npmCompromised package - containedcritical
Malicious code in npm-wold (npm)
npm-wold@1.1.1 contains malicious code in its postinstall script that fetches remote JSON from a hardcoded endpoint and dynamically invokes attacker-controlled functions with attacker-supplied arguments, enabling code execution at install time.
npmCompromised package