Which versions of buyerdashboard are malicious?

The following npm versions of buyerdashboard are flagged malicious: 45.3.4. Treat any of these as compromised.

How do I remediate buyerdashboard if I installed it?

Remove buyerdashboard from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

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

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

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

Search your lockfiles and build artifacts for buyerdashboard (version 45.3.4).

Malicious package

buyerdashboardnpm

Advisory published Oct 15, 2026Updated Oct 16, 2026

buyerdashboard is a confirmed malicious npm package (MAL-2026-17893) that executes malicious code on install (malicious version 45.3.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in buyerdashboard (npm)

MAL-2026-17893

Immediate action

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

npm uninstall buyerdashboard

What this malware does

[email protected] describes itself as "User dashboard IP info". Its preinstall hook runs node index.js on npm install and requests https://realwbx.com/ip.php?ip=8.8.8.8 with the hardcoded Authorization value 8eb5e8641a5795b022d68e14d8858415, which differs from the value in each of the account's other packages. The npm account conx3993 published it on 2026-10-15, one of 9 packages from that account between 2026-09-30 and 2026-10-15 whose preinstall hook calls realwbx.com.

Malicious versions

1 flagged

45.3.4

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for buyerdashboard (version 45.3.4).
If you installed it — respond
Remove buyerdashboard from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If buyerdashboard 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. buyerdashboard on npm has been identified as a malicious package (version 45.3.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

npmjs.com

Credits

InvisiRisk, Inc. · finder

Detect & block this

O3 blocks buyerdashboard-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database