Malware in @peptideventure/peptide-unit
Malware discovered in the npm package @peptideventure/peptide-unit. 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
- @peptideventure/peptide-unit
A malware-containing version of the npm package @peptideventure/peptide-unit has been identified and published to the npm registry. The package grants full control of affected systems to an outside entity.\n\nAny computer with this package installed or running should be considered fully compromised. The malware may provide persistent access beyond simple package removal.\n\nImmediate action is required: rotate all secrets and keys from a different, unaffected computer; remove the package; and perform comprehensive system remediation. Full removal of all malicious software cannot be guaranteed by package removal alone due to the level of system compromise.
Indicators of compromise
- Packages
- @peptideventure/peptide-unit
Remediation
- Immediately rotate all secrets, API keys, and credentials from a different, unaffected computer
- Remove the @peptideventure/peptide-unit package from all affected systems
- Perform comprehensive system audit and malware scanning on all affected computers
- Consider full system rebuild or forensic analysis if the system handles sensitive data
- Review access logs and audit trails for any unauthorized activity during the period the package was installed
- Notify any services or systems that may have been accessed from the compromised computer
Sources
- GitHub Advisory GHSA-73vr-mf4r-r3p5 · GitHub Advisory Database
Cite this entry
"Malware in @peptideventure/peptide-unit." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 14, 2026; last updated August 14, 2026. https://supplychainattack.org/incident/malware-in-peptideventure-peptide-unit-yux79q
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- containedcritical
Malicious code in 3-buildsight-web (npm)
The npm package 3-buildsight-web contains malicious code that fetches and executes arbitrary JavaScript from a remote Bitbucket URL on module load, granting full page privileges to an unverified third party.
npmCompromised package - resolvedcritical
Malicious code in @usaa-grp-personal-profile/personal-profile-common (npm)
Malicious package @usaa-grp-personal-profile/personal-profile-common version 999.0.0 published to public npm as a dependency-confusion attack targeting an organization's internal registry. The package contains preinstall and postinstall hooks that exfiltrate hostname, username, and working directory to an attacker-controlled OAST endpoint on every install.
npmDependency confusionCompromised package - resolvedcritical
Malicious code in create-coin (npm)
create-coin@20.1.1 on npm contained malicious postinstall code that collected sensitive environment variables, credentials, and host reconnaissance data. The package impersonated an esbuild platform build and exfiltrated data to a hardcoded endpoint.
npmCompromised packageTyposquatting - resolvedcritical
Malicious code in @syncraft-labs/vue (npm)
The npm package @syncraft-labs/vue version 0.4.1 contained malicious obfuscated code in its ESM build that implements a blockchain-hosted C2 dropper (EtherHiding pattern), enabling remote code execution on any consumer importing the package.
npmCompromised package