{"id":"MAL-2026-12429","revision":"1a1dfe6dad5a493ab86730ac7c61cc79","records":[{"revision":"1a1dfe6dad5a493ab86730ac7c61cc79","observedAt":"2026-10-24T13:17:17.793+00:00","statement":{"source":"osv","id":"MAL-2026-12429","aliases":[],"title":"Malicious code in rollup-plugins-check (npm)","description":"\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (5f2c7fe6586c3734730d6f8cd5ffe893c3f7cc5ff82710d1f4df22b8e76987e8)\nThe npm package rollup-plugins-check@0.0.2 declares a postinstall script (`node dist/module.js`) that, on `npm install`, performs an HTTPS GET to https://workconfig.vercel.app with `rejectUnauthorized: false` and passes the response body to `new Function('require', data)(require)`, executing the fetched code inside the installer's Node.js process with access to `require`. The remote body is opaque and controlled by whoever owns the endpoint; TLS certificate verification is explicitly disabled, so any on-path attacker can also substitute the payload. The package advertises itself as a rollup polyfill plugin and ships polyfill code copied from rollup-plugin-polyfill-node as cover, while the dropper is appended to the postinstall entry file. The name resembles the legitimate rollup-plugin-polyfill-node package.\n","state":0,"publishedAt":"2026-08-05T13:03:49+00:00","modifiedAt":"2026-08-05T13:35:52.2847609+00:00","affected":[{"ecosystem":"npm","name":"rollup-plugins-check","ranges":[],"versions":["0.0.1","0.0.2"],"rawVersionEvidence":null}],"metrics":[],"references":["https://www.npmjs.com/package/rollup-plugins-check/v/0.0.1","https://www.npmjs.com/package/rollup-plugins-check/v/0.0.2"],"sourceUrl":"https://osv.dev/vulnerability/MAL-2026-12429","license":"OSV · upstream source license applies","key":"osv:MAL-2026-12429","identifiers":["MAL-2026-12429"]},"retained":false,"historicalAffected":[]}],"coverage":[]}