Malware in peptideenv
The npm package peptideenv contains malware that grants full system compromise to an outside entity. Any computer with this package installed or running should be considered fully compromised.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- peptideenvnpm package
The npm package peptideenv has been identified as containing malware. According to the GitHub Security Advisory (GHSA-x6qh-369w-8jhf), any computer that has this package installed or running should be considered fully compromised.\n\nThe advisory indicates that all secrets and keys stored on affected computers should be rotated immediately from a different, uncompromised system. While the package should be removed, there is no guarantee that removal will eliminate all malicious software that may have been installed as a result of the initial compromise, as the attacker may have gained full control of the system.\n\nThe incident was published on 2026-07-06 via the GitHub advisory system.
Indicators of compromise
- Packages
- peptideenv
Remediation
- Immediately isolate any computer with peptideenv installed from the network
- Rotate all secrets, API keys, and credentials from a different, uncompromised computer
- Remove the peptideenv package from all affected systems
- Perform a full security audit and malware scan of affected systems
- Consider the affected systems as potentially fully compromised and plan for complete rebuild if critical systems are involved
- Review access logs and audit trails for any unauthorized activity during the period the package was installed
Sources
- GitHub Advisory GHSA-x6qh-369w-8jhf · GitHub Advisory Database
Cite this entry
"Malware in peptideenv." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 6, 2026; last updated July 6, 2026. https://supplychainattack.org/incident/malware-in-peptideenv-1b8wyk
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 test2221 (npm)
The npm package test2221 version 2.2.4 was identified as malicious by the OpenSSF Package Analysis project. The package executes commands associated with malicious behavior.
npmCompromised package - containedcritical
Malware in n8n-nodes-trust-me-im-totally-safe
Malware was discovered in the npm package n8n-nodes-trust-me-im-totally-safe, resulting in full system compromise for any computer with the package installed or running. All secrets and keys on affected systems should be rotated immediately from a different computer.
npmCompromised package - activecritical
Malware in litespeed-cache
Malware discovered in the npm package litespeed-cache. The package grants full system compromise to attackers, requiring immediate removal and credential rotation from a clean system.
npmCompromised package - containedcritical
Malware in open-worker-cli
Malware was discovered in the npm package open-worker-cli. Systems with this package installed or running should be considered fully compromised, with all secrets and keys requiring immediate rotation from a different computer.
npmCompromised package