Malicious code in gx-npm-lib (npm)
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (e919710d2f28ec776b8165821ebe2fbe480c1e432ec9416c7b73bd1315ee6a6e) Package published at version 99.99.99 under a generic name (`gx-npm-lib`) — the canonical dependency-confusion shape used to overshadow internal packages in CI version resolution. The `postinstall` lifecycle script runs `node beacon.js`, which collects installer metadata (package name, `os.hostname()`, `os.userInfo()` username, `process.cwd()`, the names of `process.env` variables, and Node version) and exfiltrates it via two channels to the hardcoded attacker-controlled OAST domain `d8uectoqtvskhftsa940pm3kth3ahdxn4.oast.me`: (1) a DNS lookup encoding `pkg.host.user` as subdomains, and (2) a base64-encoded HTTPS GET to `https://d8uectoqtvskhftsa940pm3kth3ahdxn4.oast.me/<pkg>?d=<base64>`. The package self-describes as a 'security-research placeholder' for a dependency-confusion PoC, but that self-label does not constitute installer consent — `npm install` in any environment where this package resolves (CI for an internal `gx-npm-lib`, or a developer mistyping) leaks host/user/cwd/environment inventory to the attacker's OAST collector. Multi-channel (DNS + HTTPS+base64) exfiltration to a hardcoded interactsh-style domain on a default install is a textbook active supply-chain attack. ## Source: ghsa-malware (de1b5709aec5da1ffdf3a44dcb78b36dc7aa0d65aa499feca4d6f07dd0ae6011) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
AI Analysis
Technical Summary
The gx-npm-lib package at version 99.99.99 is a malicious package published under a generic name to overshadow internal packages in CI environments, exploiting dependency confusion. Its postinstall lifecycle script runs a beacon.js script that collects installer metadata such as package name, OS hostname, user info, current working directory, environment variables, and Node.js version. This information is exfiltrated via two channels: DNS lookups encoding user and host data as subdomains, and base64-encoded HTTPS GET requests to a hardcoded attacker-controlled OAST domain. The package self-describes as a 'security-research placeholder' for a proof-of-concept, but this does not constitute consent. The default install leads to active data exfiltration, constituting a textbook supply-chain attack.
Potential Impact
Installation of this package results in unauthorized exfiltration of sensitive environment metadata from the host system to an attacker-controlled domain. This leakage can expose internal package names, hostnames, usernames, environment variables, and other contextual information, potentially aiding further attacks or reconnaissance. The attack leverages dependency confusion to trick CI systems or developers into installing the malicious package, thereby compromising the supply chain integrity.
Mitigation Recommendations
No official patch or remediation is currently documented. Users should avoid installing the gx-npm-lib package version 99.99.99. Review and restrict dependency resolution configurations in CI environments to prevent dependency confusion attacks. Monitor package sources carefully and verify package authenticity before installation. Patch status is not yet confirmed — check the vendor advisory or trusted sources for current remediation guidance.
Malicious code in gx-npm-lib (npm)
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (e919710d2f28ec776b8165821ebe2fbe480c1e432ec9416c7b73bd1315ee6a6e) Package published at version 99.99.99 under a generic name (`gx-npm-lib`) — the canonical dependency-confusion shape used to overshadow internal packages in CI version resolution. The `postinstall` lifecycle script runs `node beacon.js`, which collects installer metadata (package name, `os.hostname()`, `os.userInfo()` username, `process.cwd()`, the names of `process.env` variables, and Node version) and exfiltrates it via two channels to the hardcoded attacker-controlled OAST domain `d8uectoqtvskhftsa940pm3kth3ahdxn4.oast.me`: (1) a DNS lookup encoding `pkg.host.user` as subdomains, and (2) a base64-encoded HTTPS GET to `https://d8uectoqtvskhftsa940pm3kth3ahdxn4.oast.me/<pkg>?d=<base64>`. The package self-describes as a 'security-research placeholder' for a dependency-confusion PoC, but that self-label does not constitute installer consent — `npm install` in any environment where this package resolves (CI for an internal `gx-npm-lib`, or a developer mistyping) leaks host/user/cwd/environment inventory to the attacker's OAST collector. Multi-channel (DNS + HTTPS+base64) exfiltration to a hardcoded interactsh-style domain on a default install is a textbook active supply-chain attack. ## Source: ghsa-malware (de1b5709aec5da1ffdf3a44dcb78b36dc7aa0d65aa499feca4d6f07dd0ae6011) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
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 gx-npm-lib package at version 99.99.99 is a malicious package published under a generic name to overshadow internal packages in CI environments, exploiting dependency confusion. Its postinstall lifecycle script runs a beacon.js script that collects installer metadata such as package name, OS hostname, user info, current working directory, environment variables, and Node.js version. This information is exfiltrated via two channels: DNS lookups encoding user and host data as subdomains, and base64-encoded HTTPS GET requests to a hardcoded attacker-controlled OAST domain. The package self-describes as a 'security-research placeholder' for a proof-of-concept, but this does not constitute consent. The default install leads to active data exfiltration, constituting a textbook supply-chain attack.
Potential Impact
Installation of this package results in unauthorized exfiltration of sensitive environment metadata from the host system to an attacker-controlled domain. This leakage can expose internal package names, hostnames, usernames, environment variables, and other contextual information, potentially aiding further attacks or reconnaissance. The attack leverages dependency confusion to trick CI systems or developers into installing the malicious package, thereby compromising the supply chain integrity.
Mitigation Recommendations
No official patch or remediation is currently documented. Users should avoid installing the gx-npm-lib package version 99.99.99. Review and restrict dependency resolution configurations in CI environments to prevent dependency confusion attacks. Monitor package sources carefully and verify package authenticity before installation. Patch status is not yet confirmed — check the vendor advisory or trusted sources for current remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-6480
- Osv Schema Version
- 1.7.4
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a3ef7e027e9c7971902c5cb
Added to database: 06/26/2026, 22:06:24 UTC
Last enriched: 06/26/2026, 22:42:31 UTC
Last updated: 07/30/2026, 20:33:53 UTC
Views: 42
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.