Malicious code in express-bunker (npm)
The npm package express-bunker version 6.1.0 contains malicious code that executes a postinstall script performing an unconsented HTTP GET request to a hardcoded IP address. This request transmits the package name, version, and a fixed campaign nonce, potentially exposing environment information. The package appears to be a dependency-confusion squat targeting an internal namespace, allowing attackers to confirm successful name shadowing and enabling follow-on attacks. Although labeled as a 'benign PoC' in the README, the package performs outbound network activity during installation without user consent, and future versions could deliver arbitrary code.
AI Analysis
Technical Summary
[email protected] includes a postinstall script that unconditionally sends an HTTP GET request to a fixed external IP address over plain HTTP during npm install. The request leaks the package name, version, and a campaign nonce, signaling successful dependency-confusion exploitation against an internal namespace (yandex-geobase). This behavior discloses installer environment details to an attacker-controlled endpoint and confirms the feasibility of follow-on attacks. The package's public artifact acts as a name shadowing trap, and despite a README claiming it is a 'benign PoC,' the installer-side network communication is unauthorized and could be leveraged to deliver arbitrary malicious code in future versions.
Potential Impact
The impact includes unauthorized outbound network communication during package installation, leaking environment information such as package name and version to an attacker-controlled server. This confirms successful dependency-confusion exploitation, which could enable attackers to execute follow-on attacks. The presence of this code in the installation process violates user trust and security policies, and future versions could escalate to arbitrary code execution.
Mitigation Recommendations
No official patch or remediation is currently available. Users should avoid installing express-bunker version 6.1.0. Verify internal dependency resolution to prevent dependency confusion attacks by ensuring internal package names do not resolve to public packages. Monitor and restrict outbound network connections during package installation where possible. Check the vendor or package repository for updates or removal of the malicious package.
Malicious code in express-bunker (npm)
Description
The npm package express-bunker version 6.1.0 contains malicious code that executes a postinstall script performing an unconsented HTTP GET request to a hardcoded IP address. This request transmits the package name, version, and a fixed campaign nonce, potentially exposing environment information. The package appears to be a dependency-confusion squat targeting an internal namespace, allowing attackers to confirm successful name shadowing and enabling follow-on attacks. Although labeled as a 'benign PoC' in the README, the package performs outbound network activity during installation without user consent, and future versions could deliver arbitrary code.
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] includes a postinstall script that unconditionally sends an HTTP GET request to a fixed external IP address over plain HTTP during npm install. The request leaks the package name, version, and a campaign nonce, signaling successful dependency-confusion exploitation against an internal namespace (yandex-geobase). This behavior discloses installer environment details to an attacker-controlled endpoint and confirms the feasibility of follow-on attacks. The package's public artifact acts as a name shadowing trap, and despite a README claiming it is a 'benign PoC,' the installer-side network communication is unauthorized and could be leveraged to deliver arbitrary malicious code in future versions.
Potential Impact
The impact includes unauthorized outbound network communication during package installation, leaking environment information such as package name and version to an attacker-controlled server. This confirms successful dependency-confusion exploitation, which could enable attackers to execute follow-on attacks. The presence of this code in the installation process violates user trust and security policies, and future versions could escalate to arbitrary code execution.
Mitigation Recommendations
No official patch or remediation is currently available. Users should avoid installing express-bunker version 6.1.0. Verify internal dependency resolution to prevent dependency confusion attacks by ensuring internal package names do not resolve to public packages. Monitor and restrict outbound network connections during package installation where possible. Check the vendor or package repository for updates or removal of the malicious package.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-10500
- Osv Schema Version
- 1.7.4
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a55ff9068715ace432f4b41
Added to database: 07/14/2026, 09:21:20 UTC
Last enriched: 07/14/2026, 09:49:44 UTC
Last updated: 07/23/2026, 09:08:09 UTC
Views: 9
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.