Malicious code in bcc-design (npm)
The npm package [email protected] is a malicious dependency-confusion beacon designed to exfiltrate installer information. Upon installation, its postinstall script executes code that collects the installer's hostname and sends it, along with the package name and a timestamp, to an attacker-controlled IP address. The package does not provide any legitimate functionality and includes references to an additional network endpoint. This behavior constitutes a supply chain threat through a malicious package published at an implausibly high version to shadow internal packages.
AI Analysis
Technical Summary
[email protected] is a malicious npm package published as a dependency-confusion beacon with an implausibly high version number to shadow an internal package name. Its postinstall lifecycle script runs notify.js, which reads the operating system hostname and sends an HTTP GET request to a hardcoded IP address (http://91.201.215.48:8000/npm-poc-bcc) including the installer's hostname, package name, and a timestamp as query parameters. The package also references webhook.site in the same file. It provides no legitimate library functionality and solely serves to transmit installer identity to an attacker-controlled destination during installation.
Potential Impact
The package leaks sensitive information about the system installing it, including the hostname, which could be used for reconnaissance or further targeted attacks. The presence of a hardcoded attacker-controlled endpoint means that any installation of this package results in data exfiltration. There is no indication of code execution beyond the postinstall script or direct system compromise, but the information leak itself poses a privacy and security risk.
Mitigation Recommendations
No official patch or remediation is indicated. Users should avoid installing the bcc-design package at version 9999.0.0. Since this is a malicious package published to npm, organizations should implement supply chain security measures such as package allowlisting, verifying package provenance, and monitoring for suspicious package versions. Check the npm registry and vendor advisories for any updates or removals of this package.
Malicious code in bcc-design (npm)
Description
The npm package [email protected] is a malicious dependency-confusion beacon designed to exfiltrate installer information. Upon installation, its postinstall script executes code that collects the installer's hostname and sends it, along with the package name and a timestamp, to an attacker-controlled IP address. The package does not provide any legitimate functionality and includes references to an additional network endpoint. This behavior constitutes a supply chain threat through a malicious package published at an implausibly high version to shadow internal packages.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
[email protected] is a malicious npm package published as a dependency-confusion beacon with an implausibly high version number to shadow an internal package name. Its postinstall lifecycle script runs notify.js, which reads the operating system hostname and sends an HTTP GET request to a hardcoded IP address (http://91.201.215.48:8000/npm-poc-bcc) including the installer's hostname, package name, and a timestamp as query parameters. The package also references webhook.site in the same file. It provides no legitimate library functionality and solely serves to transmit installer identity to an attacker-controlled destination during installation.
Potential Impact
The package leaks sensitive information about the system installing it, including the hostname, which could be used for reconnaissance or further targeted attacks. The presence of a hardcoded attacker-controlled endpoint means that any installation of this package results in data exfiltration. There is no indication of code execution beyond the postinstall script or direct system compromise, but the information leak itself poses a privacy and security risk.
Mitigation Recommendations
No official patch or remediation is indicated. Users should avoid installing the bcc-design package at version 9999.0.0. Since this is a malicious package published to npm, organizations should implement supply chain security measures such as package allowlisting, verifying package provenance, and monitoring for suspicious package versions. Check the npm registry and vendor advisories for any updates or removals of this package.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-14117
- Osv Schema Version
- 1.7.4
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a8460a5c6e8be033245ab7e
Added to database: 08/18/2026, 13:39:49 UTC
Last enriched: 08/18/2026, 13:45:06 UTC
Last updated: 08/18/2026, 23:49:33 UTC
Views: 6
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.