{"id":"MAL-2026-14295","revision":"d2d3568a3e424060ba530055bafe1166","records":[{"revision":"d2d3568a3e424060ba530055bafe1166","observedAt":"2026-10-24T13:17:17.793+00:00","statement":{"source":"osv","id":"MAL-2026-14295","aliases":[],"title":"Malicious code in mcp-dev-toolkit (npm)","description":"\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (eea6d82bd4d62a015c59af54ac277d0381c43203b3475ef1137e57893e67126c)\nPackage mcp-dev-toolkit@1.5.0 contains multiple files whose behavior matches operational malware rather than a developer toolkit. index.js collects host identity data (os.hostname(), cwd, version) and serializes it via JSON.stringify for outbound transmission. spread.js imports child_process alongside https.request and issues outbound GET traffic with hostname/process data. c2_exfil.js (the filename itself declares its purpose) imports child_process and invokes execSync('git push...'), a self-propagation shape that pushes content from the installer's environment to a remote git destination. The combination of a file explicitly named c2_exfil.js, host-identifier collection wired to an HTTPS client, and execSync-driven git push is not consistent with any legitimate 'dev toolkit' function and represents installer-side reconnaissance, exfiltration, and code-propagation on install or import.\n","state":0,"publishedAt":"2026-08-19T08:16:01+00:00","modifiedAt":"2026-08-19T09:00:20.5795543+00:00","affected":[{"ecosystem":"npm","name":"mcp-dev-toolkit","ranges":[],"versions":["1.5.0"],"rawVersionEvidence":null}],"metrics":[],"references":["https://www.npmjs.com/package/mcp-dev-toolkit/v/1.5.0"],"sourceUrl":"https://osv.dev/vulnerability/MAL-2026-14295","license":"OSV · upstream source license applies","key":"osv:MAL-2026-14295","identifiers":["MAL-2026-14295"]},"retained":false,"historicalAffected":[]}],"coverage":[]}