Threat Intelligence Database

--- _-= 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.

--- _-= 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.

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (7fcad1b944d9ceb92389673398df9f471911a788fe608774a3298c69900bb1c7) [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. ## 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.