Which versions of xerohub-discord-voice-v2 are malicious?

The following npm versions of xerohub-discord-voice-v2 are flagged malicious: 1.8.0. Treat any of these as compromised.

How do I remediate xerohub-discord-voice-v2 if I installed it?

xerohub-discord-voice-v2 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 xerohub-discord-voice-v2 — how do I know if it already compromised me?

If xerohub-discord-voice-v2 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 xerohub-discord-voice-v2 part of a known attack campaign?

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

Malicious package

xerohub-discord-voice-v2npm

xerohub-discord-voice-v2 is a confirmed malicious npm package (MAL-2026-11154) that steals credentials and exfiltrates sensitive data (malicious version 1.8.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in xerohub-discord-voice-v2 (npm)

MAL-2026-11154

Immediate action

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

npm uninstall xerohub-discord-voice-v2

What this malware does

The package advertises a Discord voice client via an exported startVoiceJoiner(config) API. When a caller invokes it with their Discord credentials, Xerohub_Voice.js validates the supplied USER_TOKEN and then POSTs USER_TOKEN, USER_TOKEN_2, VOICE_SERVER_ID/SERVER_ID and VOICE_CHANNEL_ID via axios to a hardcoded Discord webhook URL (https://discord.com/api/webhooks/1528726419046404196/...) that the caller never configured. A source comment explicitly states that errors from this POST are swallowed so the user does not notice. Discord user tokens are full account credentials; forwarding them silently to an author-controlled destination is credential theft and account takeover of the calling user.

Malicious versions

1 flagged

1.8.0

Indicators of compromise (SHA-256)

cf9b6541cc4324cf5972b8544d673b91874dac770763bac335d3c8900292dfcd

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

Campaign

IN-MAL-2026-010876

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks xerohub-discord-voice-v2-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