{"id":"MAL-2026-14196","revision":"f40ef2e92d3745e092823bf80dbe0341","records":[{"revision":"f40ef2e92d3745e092823bf80dbe0341","observedAt":"2026-10-24T13:17:17.793+00:00","statement":{"source":"osv","id":"MAL-2026-14196","aliases":[],"title":"Malicious code in tfjs-custom-module (npm)","description":"\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (c50d87a4593cb5a0444f2333f368180b64dfb5d3b8f37e0baf4f6d686ea2ef74)\ntfjs-custom-module is a typosquat of the tensorflow/tfjs package. Its package.json declares a postinstall lifecycle script that runs automatically on npm install. The script collects installer host identifiers — os.hostname(), process.platform, process.arch, process.version, package name, and the npm lifecycle event — and POSTs them as JSON via https.request to the hardcoded external host 8xq4kw5d.instances.poc.jchunt.top at path /tfjs-custom-module. The endpoint is not the installer's infrastructure and the beacon is not opt-in. This is host-reconnaissance exfiltration to an author-controlled destination running under a look-alike canary domain, regardless of any self-labeling as security research.\n","state":0,"publishedAt":"2026-08-19T01:17:36+00:00","modifiedAt":"2026-08-19T01:45:11.5047141+00:00","affected":[{"ecosystem":"npm","name":"tfjs-custom-module","ranges":[],"versions":["1.0.0"],"rawVersionEvidence":null}],"metrics":[],"references":["https://www.npmjs.com/package/tfjs-custom-module/v/1.0.0"],"sourceUrl":"https://osv.dev/vulnerability/MAL-2026-14196","license":"OSV · upstream source license applies","key":"osv:MAL-2026-14196","identifiers":["MAL-2026-14196"]},"retained":false,"historicalAffected":[]}],"coverage":[]}