Which versions of pergel are malicious?

The following npm versions of pergel are flagged malicious: 0.13.2. Treat any of these as compromised.

How do I remediate pergel if I installed it?

pergel is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed pergel — how do I know if it already compromised me?

If pergel 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.

Is pergel part of a known attack campaign?

Yes — pergel is associated with the GHSA-2w5p-9qrr-g23p campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find pergel across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for pergel (version 0.13.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pergel across your stack and pipelines.

Malicious package

pergelnpm

Malicious code in pergel (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191138

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall pergel

What this malware does

The package pergel was found to contain malicious 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.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

1 flagged

0.13.2

Indicators of compromise (SHA-256)

013990a2334d492668cc0d60833e3b2a30e9578b49ca1d8a75f904b5c82e1932

1ec6f4c969047a8c9326a633c1389d7d08678a47f8f0f36ae012d91f1ceac182

0beb04dcc264a7b8ea3f1b3c48c402609868184158f6bd8615a1f81fc5a29315

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for pergel (version 0.13.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pergel across your stack and pipelines.
If you installed it — respond
pergel is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If pergel 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 pergel 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

No. pergel on npm has been identified as a malicious package (version 0.13.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-2w5p-9qrr-g23p

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks pergel-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring