{"id":"MAL-2026-12511","revision":"4f65050d367546a5b5268f134b0596b8","records":[{"revision":"4f65050d367546a5b5268f134b0596b8","observedAt":"2026-10-24T13:17:17.793+00:00","statement":{"source":"osv","id":"MAL-2026-12511","aliases":[],"title":"Malicious code in application_base (npm)","description":"\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (73797279861276dbe0ee846487e1a6c4206ae7c5c97cf5c18b478d78d9f2ffb7)\napplication_base@9999.0.0 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.\n","state":0,"publishedAt":"2026-08-05T13:17:43+00:00","modifiedAt":"2026-08-05T14:35:12.6828472+00:00","affected":[{"ecosystem":"npm","name":"application_base","ranges":[],"versions":["9999.0.0"],"rawVersionEvidence":null}],"metrics":[],"references":["https://www.npmjs.com/package/application_base/v/9999.0.0"],"sourceUrl":"https://osv.dev/vulnerability/MAL-2026-12511","license":"OSV · upstream source license applies","key":"osv:MAL-2026-12511","identifiers":["MAL-2026-12511"]},"retained":false,"historicalAffected":[]}],"coverage":[]}