{"id":"MAL-2026-14218","revision":"a5029e91a93740f38748b4f3500bd5e1","records":[{"revision":"a5029e91a93740f38748b4f3500bd5e1","observedAt":"2026-10-24T13:17:17.793+00:00","statement":{"source":"osv","id":"MAL-2026-14218","aliases":[],"title":"Malicious code in mapkit-loader (npm)","description":"\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (cb2d3c3e234b52b2bbffe7b197f9ec483b2b574667543338b975c99831633c86)\nUnscoped npm package 'mapkit-loader' impersonates the scoped '@apple/mapkit-loader' to intercept mistyped `npx mapkit-loader` invocations. The package.json self-describes as a 'PoC' targeting that confusion. On `npm install`, the postinstall lifecycle script (postinstall.js) unconditionally issues an HTTPS POST to a hardcoded third-party endpoint at npx-monitor-76056.azurewebsites.net/api/pingback carrying a persistent UUID, package version, trigger source ('npm-postinstall'), and timestamp. The UUID is written to ~/.cache/.mapkit-loader-id so subsequent executions (including the bin entry) can be correlated back to the same host. No credential or filesystem exfiltration is present, but the combination of name-confusion targeting an official Apple scope plus install-time beaconing to an author-controlled endpoint is a supply-chain typosquat with an operational tracking channel.\n","state":0,"publishedAt":"2026-08-19T03:16:17+00:00","modifiedAt":"2026-08-19T03:30:15.9554055+00:00","affected":[{"ecosystem":"npm","name":"mapkit-loader","ranges":[],"versions":["1.0.0"],"rawVersionEvidence":null}],"metrics":[],"references":["https://www.npmjs.com/package/mapkit-loader/v/1.0.0"],"sourceUrl":"https://osv.dev/vulnerability/MAL-2026-14218","license":"OSV · upstream source license applies","key":"osv:MAL-2026-14218","identifiers":["MAL-2026-14218"]},"retained":false,"historicalAffected":[]}],"coverage":[]}