Malicious code in gx-npm-ui (npm)
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (04e5ac6b8b24f2c158c37d3d6ac268bbf7f472433660064491538ee468cfcfcb) Package published at version 99.99.99 under the gx-npm-* namespace, a shape designed to win npm version resolution against private internal packages of the same name. package.json declares postinstall=`node beacon.js`, which runs unconditionally on `npm install`. beacon.js collects the installer's hostname, OS username, current working directory, package name, Node version, and the first 80 environment variable names, then exfiltrates them two ways to the hardcoded out-of-band host `d8uectoqtvskhftsa940pm3kth3ahdxn4.oast.me`: (1) a DNS lookup encoding the collected identifiers as subdomain labels, and (2) an HTTPS GET with a base64-encoded JSON payload in the query string. Any CI/build system or developer machine that resolves this package against the public npm registry leaks host identity and environment-variable names to an attacker-controlled interactsh/OAST endpoint on every install. ## Source: ghsa-malware (40016c94d5d31e1314b1f462b5fb83ae7ce15121df43474ce3440749ab89e72e) 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-ui npm package at version 99.99.99 includes a postinstall script that executes beacon.js unconditionally on npm install. This script gathers the installer's hostname, OS username, current working directory, package name, Node.js version, and the first 80 environment variable names. It then exfiltrates this information to a hardcoded attacker-controlled domain using two methods: DNS queries encoding the data as subdomains and HTTPS GET requests with base64-encoded JSON payloads in the query string. This results in leakage of host identity and environment details to an external malicious endpoint on every installation.
Potential Impact
Systems that install the affected gx-npm-ui package version 99.99.99 leak sensitive environment and host information to an attacker-controlled server. This exposure can compromise privacy and potentially aid attackers in further targeting or reconnaissance. The data exfiltration occurs silently during installation, affecting developer machines and CI/build systems that resolve this package from the public npm registry.
Mitigation Recommendations
No official patch or remediation is currently available for this malicious package version. Users should avoid installing gx-npm-ui version 99.99.99 from the public npm registry. Verify package provenance and use trusted sources or internal mirrors to prevent installation of malicious packages. Monitor package dependencies for suspicious versions and remove or replace any instances of this package.
Malicious code in gx-npm-ui (npm)
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (04e5ac6b8b24f2c158c37d3d6ac268bbf7f472433660064491538ee468cfcfcb) Package published at version 99.99.99 under the gx-npm-* namespace, a shape designed to win npm version resolution against private internal packages of the same name. package.json declares postinstall=`node beacon.js`, which runs unconditionally on `npm install`. beacon.js collects the installer's hostname, OS username, current working directory, package name, Node version, and the first 80 environment variable names, then exfiltrates them two ways to the hardcoded out-of-band host `d8uectoqtvskhftsa940pm3kth3ahdxn4.oast.me`: (1) a DNS lookup encoding the collected identifiers as subdomain labels, and (2) an HTTPS GET with a base64-encoded JSON payload in the query string. Any CI/build system or developer machine that resolves this package against the public npm registry leaks host identity and environment-variable names to an attacker-controlled interactsh/OAST endpoint on every install. ## Source: ghsa-malware (40016c94d5d31e1314b1f462b5fb83ae7ce15121df43474ce3440749ab89e72e) 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-ui npm package at version 99.99.99 includes a postinstall script that executes beacon.js unconditionally on npm install. This script gathers the installer's hostname, OS username, current working directory, package name, Node.js version, and the first 80 environment variable names. It then exfiltrates this information to a hardcoded attacker-controlled domain using two methods: DNS queries encoding the data as subdomains and HTTPS GET requests with base64-encoded JSON payloads in the query string. This results in leakage of host identity and environment details to an external malicious endpoint on every installation.
Potential Impact
Systems that install the affected gx-npm-ui package version 99.99.99 leak sensitive environment and host information to an attacker-controlled server. This exposure can compromise privacy and potentially aid attackers in further targeting or reconnaissance. The data exfiltration occurs silently during installation, affecting developer machines and CI/build systems that resolve this package from the public npm registry.
Mitigation Recommendations
No official patch or remediation is currently available for this malicious package version. Users should avoid installing gx-npm-ui version 99.99.99 from the public npm registry. Verify package provenance and use trusted sources or internal mirrors to prevent installation of malicious packages. Monitor package dependencies for suspicious versions and remove or replace any instances of this package.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-6481
- Osv Schema Version
- 1.7.4
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a3ef7e227e9c7971903209b
Added to database: 06/26/2026, 22:06:26 UTC
Last enriched: 06/26/2026, 22:42:35 UTC
Last updated: 07/25/2026, 18:10:19 UTC
Views: 53
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.