{"id":"MAL-2026-12175","revision":"fd5bc5d9a05a424db587ac0cc0ff2dc9","records":[{"revision":"fd5bc5d9a05a424db587ac0cc0ff2dc9","observedAt":"2026-10-24T13:17:17.793+00:00","statement":{"source":"osv","id":"MAL-2026-12175","aliases":[],"title":"Malicious code in datefmt-pro (npm)","description":"\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (addca973f3384757b9ff2e00e5becd70e509ef5233c4cd2dc6ce73019b467787)\ndatefmt-pro presents itself as a date formatting utility, but its actual behavior is an install-time reconnaissance beacon. The scripts.postinstall entry runs postinstall.js on npm install, which uses child_process.execSync to run hostname, whoami, uname -a, and pwd, and calls os.networkInterfaces() to enumerate non-internal IPv4 addresses. It then POSTs the collected identity and internal network information as JSON over plain HTTP to the hardcoded bare-IP endpoint http://129.204.76.212:9999/rce-poc. index.js contains only a trivial date-formatting stub whose in-source comments state it exists to make the package look like a real date library while the payload lives in postinstall.js. The package name imitates a plausible utility to attract installers via typo/trust; the advertised purpose does not require any host reconnaissance or outbound network activity at install time.\n","state":0,"publishedAt":"2026-08-05T09:10:03+00:00","modifiedAt":"2026-08-05T14:36:17.4379735+00:00","affected":[{"ecosystem":"npm","name":"datefmt-pro","ranges":[],"versions":["1.0.2","1.0.0","1.0.1"],"rawVersionEvidence":null}],"metrics":[],"references":["https://www.npmjs.com/package/datefmt-pro/v/1.0.2","https://www.npmjs.com/package/datefmt-pro/v/1.0.0","https://www.npmjs.com/package/datefmt-pro/v/1.0.1"],"sourceUrl":"https://osv.dev/vulnerability/MAL-2026-12175","license":"OSV · upstream source license applies","key":"osv:MAL-2026-12175","identifiers":["MAL-2026-12175"]},"retained":false,"historicalAffected":[]}],"coverage":[]}