bcc-designnpm
bcc-design is a confirmed malicious npm package (MAL-2026-14117) that opens a backdoor for remote access (malicious version 9999.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bcc-design (npm)
What this malware does
[email protected] is a dependency-confusion beacon package published at an implausibly high version to shadow an internal package name. On npm install, its postinstall lifecycle script executes notify.js, which reads os.hostname() and issues an HTTP GET to the hardcoded bare-IP endpoint http://91.201.215.48:8000/npm-poc-bcc carrying the installer's hostname, the package name, and a timestamp as query parameters. A second network reference to webhook.site is present in the same file. The package provides no legitimate library functionality; its only install-time effect is transmitting installer identity to an attacker-controlled destination.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Backdoor / remote accessFind it
Search your lockfiles and build artifacts for bcc-design (version 9999.0.0).
If you installed it — respond
bcc-design establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If bcc-design 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
Campaign
References
Credits
- Amazon Inspector · finder
- ReversingLabs · finder
Detect & block this
O3 blocks bcc-design-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.