@peptide-packets/js-unimodenpm
@peptide-packets/js-unimode is a confirmed malicious npm package (MAL-2026-11447) that executes malicious code on install (malicious version 1.1.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @peptide-packets/js-unimode (npm)
What this malware does
index.js in @peptide-packets/js-unimode exposes a listMods() function that decodes a base64-encoded URL pointing to a GitHub gist owned by user emmettesjunitya, fetches the gist's first file via the GitHub API, and passes the returned text directly to eval(). Any consumer that calls listMods() executes whatever JavaScript the gist owner has published at that moment, in-process, with full privileges of the host application. The gist is mutable and attacker-controlled: today's content can be replaced without any change to this package. The dropper URL is base64-encoded and placed on the same source line as the end of an unrelated for-loop after a long run of trailing whitespace, concealing the block from casual review. The package presents itself as a proteomics data helper and has no documented purpose that requires fetching or evaluating remote code.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @peptide-packets/js-unimode (version 1.1.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @peptide-packets/js-unimode across your stack and pipelines.
If you installed it — respond
Remove @peptide-packets/js-unimode from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If @peptide-packets/js-unimode was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @peptide-packets/js-unimode before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks @peptide-packets/js-unimode-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.