{"id":"MAL-2026-16304","revision":"29273b470fbe451e9015a56c7681aade","records":[{"revision":"29273b470fbe451e9015a56c7681aade","observedAt":"2026-10-24T13:17:17.793+00:00","statement":{"source":"osv","id":"MAL-2026-16304","aliases":[],"title":"Malicious code in @nimbusedge2/authxsas1 (npm)","description":"\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (0b27280b8f4c1e044e49b77e58c7c8de895a002f51be51756bc40e909d3f6fa1)\npackage.json declares a preinstall lifecycle script that runs automatically on `npm install`. The script uses curl to fetch the cloud instance metadata service (169.254.169.254, accessed via the nip.io wildcard-DNS wrapper `169.254.169.254.nip.io/latest/meta-data/`), base64-encodes the response, and POSTs it to a hardcoded third-party endpoint at http://canarytokens.com/terms/7dc94zmd3so67n5vbz5bxmt7v/contact.php. On cloud and CI installers this discloses instance identity metadata and, where IMDSv1 is reachable, temporary IAM credentials to the destination. The package's description field self-labels the beacon as an 'Authorized report' with a wearehackerone.com contact address; that label is author-controlled and does not change the behavior class — installing the package causes installer-side host and cloud metadata to be sent off-host to a canarytoken beacon.\n","state":0,"publishedAt":"2026-09-21T03:06:48+00:00","modifiedAt":"2026-09-21T03:30:17.6354259+00:00","affected":[{"ecosystem":"npm","name":"@nimbusedge2/authxsas1","ranges":[],"versions":["1.1.0"],"rawVersionEvidence":null}],"metrics":[],"references":["https://www.npmjs.com/package/@nimbusedge2/authxsas1/v/1.1.0"],"sourceUrl":"https://osv.dev/vulnerability/MAL-2026-16304","license":"OSV · upstream source license applies","key":"osv:MAL-2026-16304","identifiers":["MAL-2026-16304"]},"retained":false,"historicalAffected":[]}],"coverage":[]}