{"id":"MAL-2026-13453","revision":"4c4fe0c2985b4fe0a2ecd60c9961e361","records":[{"revision":"4c4fe0c2985b4fe0a2ecd60c9961e361","observedAt":"2026-10-24T13:17:17.793+00:00","statement":{"source":"osv","id":"MAL-2026-13453","aliases":["GHSA-r69p-2jjg-vh25"],"title":"Malicious code in pilgrimage-portal-client (npm)","description":"\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (73b9f604c074795de9d79071f9e8a6c131e0a30159f6ea2a0769ded3df6d5a28)\nOn `npm install`, the package's postinstall hook runs `node ping.js`, which reads the installer's hostname via `require('os').hostname()` and POSTs it, along with a timestamp and the package name/version, to the hardcoded bare-IP endpoint http://134.119.222.10:9009/canary over plain HTTP. Errors and timeouts are silently swallowed. The version number (99.0.0) and beacon shape are consistent with a dependency-confusion proof-of-install callback: the destination is a non-first-party bare IP the installer never configured, and the outbound call fires automatically without user consent. Regardless of the 'canary' self-label, host-identifier data leaves the installer's machine to an attacker-controlled endpoint at install time.\n","state":0,"publishedAt":"2026-08-06T16:22:23+00:00","modifiedAt":"2026-09-24T09:30:16.618988+00:00","affected":[{"ecosystem":"npm","name":"pilgrimage-portal-client","ranges":[],"versions":["99.0.0"],"rawVersionEvidence":null}],"metrics":[],"references":["https://www.npmjs.com/package/pilgrimage-portal-client/v/99.0.0","https://github.com/advisories/GHSA-r69p-2jjg-vh25"],"sourceUrl":"https://osv.dev/vulnerability/MAL-2026-13453","license":"OSV · upstream source license applies","key":"osv:MAL-2026-13453","identifiers":["MAL-2026-13453","GHSA-r69p-2jjg-vh25"]},"retained":false,"historicalAffected":[]}],"coverage":[]}