Malicious code in @flipbit2-bb/test-auth-state (npm)
The npm package @flipbit2-bb/test-auth-state version 0.0.2 contains malicious code that executes a postinstall script collecting host identifiers and sending them to an external webhook. The package masquerades as an internal Atlassian package to exploit dependency confusion. Installation of this package can lead to full system compromise, requiring immediate secret and key rotation and package removal.
AI Analysis
Technical Summary
The npm package @flipbit2-bb/[email protected] includes a postinstall script (phone-home.js) that collects system information such as hostname, username, platform, OS release, timestamp, and package label, then sends this data via HTTPS GET to an external webhook URL. The package is crafted to impersonate an internal Atlassian package (@atlassiansox/[email protected]) to exploit dependency confusion, increasing the likelihood of installation in environments expecting the internal package. The malicious payload leaks sensitive host identifiers and potentially compromises the system. According to the source, any system with this package installed or running should be considered fully compromised, with all secrets and keys rotated immediately from a separate, trusted system. Removal of the package alone may not eliminate all malicious components.
Potential Impact
Installation of this package results in leakage of host identifiers to an attacker-controlled endpoint and may lead to full system compromise. The attacker may gain control over the affected system, risking exposure of all stored secrets and keys. The compromise is severe enough that secret rotation and comprehensive remediation are required. The package itself has no legitimate functionality and serves solely as a malicious payload.
Mitigation Recommendations
Remove the @flipbit2-bb/test-auth-state package version 0.0.2 immediately. Rotate all secrets and keys stored on the affected system from a separate, trusted environment. Because full system compromise is possible, assume that removal of the package alone may not fully remediate the system; consider rebuilding or thoroughly auditing the system for persistence mechanisms. Monitor for any unexpected network connections or processes related to this package. There is no official patch or fix; avoidance and removal are the primary mitigations.
Malicious code in @flipbit2-bb/test-auth-state (npm)
Description
The npm package @flipbit2-bb/test-auth-state version 0.0.2 contains malicious code that executes a postinstall script collecting host identifiers and sending them to an external webhook. The package masquerades as an internal Atlassian package to exploit dependency confusion. Installation of this package can lead to full system compromise, requiring immediate secret and key rotation and package removal.
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
The npm package @flipbit2-bb/[email protected] includes a postinstall script (phone-home.js) that collects system information such as hostname, username, platform, OS release, timestamp, and package label, then sends this data via HTTPS GET to an external webhook URL. The package is crafted to impersonate an internal Atlassian package (@atlassiansox/[email protected]) to exploit dependency confusion, increasing the likelihood of installation in environments expecting the internal package. The malicious payload leaks sensitive host identifiers and potentially compromises the system. According to the source, any system with this package installed or running should be considered fully compromised, with all secrets and keys rotated immediately from a separate, trusted system. Removal of the package alone may not eliminate all malicious components.
Potential Impact
Installation of this package results in leakage of host identifiers to an attacker-controlled endpoint and may lead to full system compromise. The attacker may gain control over the affected system, risking exposure of all stored secrets and keys. The compromise is severe enough that secret rotation and comprehensive remediation are required. The package itself has no legitimate functionality and serves solely as a malicious payload.
Mitigation Recommendations
Remove the @flipbit2-bb/test-auth-state package version 0.0.2 immediately. Rotate all secrets and keys stored on the affected system from a separate, trusted environment. Because full system compromise is possible, assume that removal of the package alone may not fully remediate the system; consider rebuilding or thoroughly auditing the system for persistence mechanisms. Monitor for any unexpected network connections or processes related to this package. There is no official patch or fix; avoidance and removal are the primary mitigations.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-4389
- Osv Schema Version
- 1.7.4
- Aliases
- ["GHSA-jrpc-qv6v-wmr6"]
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a42ed2927e9c79719934b1e
Added to database: 06/29/2026, 22:09:45 UTC
Last enriched: 06/29/2026, 22:20:25 UTC
Last updated: 07/18/2026, 17:27:21 UTC
Views: 7
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.