Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
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 versions 1.0.0, 1.2.0, 1.3.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

xerohub-discord-voice-v2 advertises itself as a Discord voice-channel joiner but its exported startVoiceJoiner() flow covertly forwards the caller's Discord USER_TOKEN and USER_TOKEN_2 (raw Discord account credentials), along with username, server and channel identifiers, to a hardcoded author-controlled Discord webhook constant DEVELOPER_BACKEND_WEBHOOK via a sendToDeveloperBackend() helper in Xerohub_Voice.js. In version 1.9.0 the webhook URL is still the literal placeholder 'https://discord.com/api/webhooks/YOUR_DEV_WEBHOOK_ID/YOUR_DEV_WEBHOOK_TOKEN' and a guard short-circuits the axios.post call, so no tokens leave the machine in this specific version — but the exfiltration path is fully implemented and only requires the author to substitute a real webhook ID and token in a subsequent publish for every caller's Discord credentials to be silently transmitted. The package also depends on discord.js-selfbot-v13 and drives a selfbot Client using the user's raw account token, indicating the intended targets are users pasting real Discord account credentials rather than bot tokens. Thai-language comments in the source describe the mechanism as a hidden 'developer backend'. The covert relay of caller-supplied account credentials to an author endpoint conflicts with the package's stated purpose as a voice joiner.

Malicious versions

16 flagged
1.0.01.2.01.3.01.4.01.5.01.6.01.7.01.8.01.9.02.1.02.2.02.3.02.4.02.5.02.6.02.7.0

Indicators of compromise (SHA-256)

cf9b6541cc4324cf5972b8544d673b91874dac770763bac335d3c8900292dfcd
1d3b956e561364b5946652654802761572f9adec882e0310d31f26ac8e032310
89472a6e52613058ddf64e3b4ae4228a04b8bfa7fa6a75bd70364c6387a8fc4e
9a9c075d2e98d863ae20c31c114936fd16d6ff3abe0e52f78ef366eb165ce716
c492698d0815abeaa486c8e61c5d4a29d56ffaf7f5d9fbaf465496b12a42bfaf
082f90d492eb917644dd44d1ebc7befa5557488e188174ed04241b8163d547ac
3837c62fcf0813092b1bf51eaf6f47ffd9477d8b4aa9c9e02a42de7ea466ba95
86630f2d32ad3a1a8ae419e538be3c6b46ce5f64ea5e871e1ccdf34c402d0032
ae2ea1c3851cbf6d3ffa6a3b698dad72436ba200f7a6dbf41c7477b2f0ef808a
b59063377466896bea6fd9d2eef88fb4450917540c1e5214a6c25ce08de3974c
c64830f9cd9a4d705686a5ee08a344e3fd146ab965053dda6e625542388ad487
066cb7d27a71055b89630648ee5ae6eed64d6db93e883de66a5db678cfa7663c
17bcb0422625a11dccf623f7b4a05250edceb66a10ea72be5aa9262ca5c2ad05
318f3b17f9ba6d30a0c0a84fcabb0b6bdb713b33b6edc77d61d3cc62c4c2da54
3995f5c811df7a41cb6945af1307b04bea934e81188c13705df67c697d4fcb96
41890416e5f78be022ddc5de2d56a915bc75403e07878176a057cacc6fd410d1

Detection & response playbook

Credential / info stealer
  1. 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 (16 malicious versions). 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.

  2. 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.

  3. 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.

  4. 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 (versions 1.0.0, 1.2.0, 1.3.0, 1.4.0, 1.5.0, 1.6.0, 1.7.0, 1.8.0, and 8 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010876IN-MAL-2026-014953IN-MAL-2026-014952IN-MAL-2026-014954IN-MAL-2026-014951IN-MAL-2026-014958IN-MAL-2026-014957IN-MAL-2026-014955IN-MAL-2026-014956IN-MAL-2026-014959IN-MAL-2026-017277IN-MAL-2026-017278IN-MAL-2026-017274IN-MAL-2026-017273IN-MAL-2026-017275IN-MAL-2026-017276

References

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.

Explore

xerohub-discord-voice-v2 (npm) malicious package — MAL-2026-11154 | O3 Security