Malicious code in application_base (npm)
Exploitation and risk
Source statusCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
Which CVEs have scores here?
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
osv · MAL-2026-12511
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (73797279861276dbe0ee846487e1a6c4206ae7c5c97cf5c18b478d78d9f2ffb7) [email protected] runs callback.js from its preinstall lifecycle hook on `npm install`. The script collects os.hostname(), os.userInfo().username, process.cwd(), the configured npm registry, and CI repo-slug environment variables (GITHUB_REPOSITORY, CI_PROJECT_PATH, BUILD_REPOSITORY_NAME, BITBUCKET_REPO_FULL_NAME, TRAVIS_REPO_SLUG, DRONE_REPO, BUILDKITE_PIPELINE_SLUG, CIRCLE_PROJECT_REPONAME, JOB_NAME), and issues an HTTP GET to http://75.119.137.232:31337/depconfuse with those values as query parameters. The bare-IP plain-HTTP destination is not a first-party telemetry endpoint. Combined with the 9999.0.0 version overshoot and the `depconfuse` path, this is a dependency-confusion reconnaissance beacon: it signals to the attacker whether an internal package name resolved to their public registry entry inside a target's build environment, along with the host, user, working directory, and CI repository identity needed to target that organization for a follow-on internal-package hijack.
- Source published
- 5 Aug 2026 13:17:43 UTC
- Source modified
- 5 Aug 2026 14:35:12 UTC
- Saved here
- 24 Oct 2026 13:17:17 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.