Which versions of wenk are malicious?

The following npm versions of wenk are flagged malicious: 1.0.9, 1.0.10. Treat any of these as compromised.

How do I remediate wenk if I installed it?

wenk 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 wenk — how do I know if it already compromised me?

If wenk was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is wenk part of a known attack campaign?

Yes — wenk is associated with the GHSA-hjhr-87pr-r7vw 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 wenk across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for wenk (2 malicious versions).

Malicious package

wenknpm

Advisory published Nov 24, 2025Updated Dec 1, 2025

wenk is a confirmed malicious npm package (MAL-2025-191155) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.9, 1.0.10). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in wenk (npm)

MAL-2025-191155

Immediate action

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

npm uninstall wenk

What this malware does

The package wenk 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

2 flagged

1.0.91.0.10

Indicators of compromise (SHA-256)

440c248dbbb7a7c4fb5db4f70f71b5dd51ca4287f3d4e83c7caceeab7aee2dd8

daf519593af9db3c436148ea8f89fbd87c672d70263c66f04e3741237141fd0d

209b9df1ab21f1d5e193a2a9e68ece62122dc7979592c1f21599dd018aebfff7

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for wenk (2 malicious versions).
If you installed it — respond
wenk 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 wenk was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. wenk on npm has been identified as a malicious package (versions 1.0.9, 1.0.10 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-hjhr-87pr-r7vw

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks wenk-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

Explore

All malware advisories How O3 detects malware Vulnerability database