Which versions of wolverinechat are malicious?

The following npm versions of wolverinechat are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate wolverinechat if I installed it?

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

If wolverinechat 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 wolverinechat part of a known attack campaign?

Yes — wolverinechat is associated with the IN-MAL-2026-014923 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 wolverinechat 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 wolverinechat (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging wolverinechat across your stack and pipelines.

Malicious package

wolverinechatnpm

wolverinechat is a confirmed malicious npm package (MAL-2026-12816) that steals credentials and exfiltrates sensitive data (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in wolverinechat (npm)

MAL-2026-12816

Immediate action

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

npm uninstall wolverinechat

What this malware does

package.json declares a preinstall hook that runs index.js during npm install. The script reads /etc/passwd, /etc/hosts, os.hostname(), os.userInfo().username, the user's home directory, dns.getServers(), and package metadata, then POSTs the collected data via HTTPS to the hardcoded subdomain 7ckdbwo9f8dtrg8y36sbe4e8lzrqfg35.oastify.com (Burp Collaborator OAST callback). The exfiltration fires automatically at install time without user interaction.

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

6ad1c6bad5ee8d3cb562503b94d5534ba2c98ad5b4854c073e1482d59ab8687e

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 wolverinechat (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging wolverinechat across your stack and pipelines.
If you installed it — respond
wolverinechat 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 wolverinechat 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 wolverinechat 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. wolverinechat on npm has been identified as a malicious package (version 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014923

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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