mapkit-loader
⚠️ SECURITY RESEARCH — Apple Bug Bounty npx confusion PoC. The correct package is @apple/mapkit-loader.
This report shows the evidence for mapkit-loader@1.0.1. 2 of 4 known versions are blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.
AI Security Review
scanned 4mo ago · by lpm-firewall-aiDirect source inspection confirms unconsented install-time network beaconing in a dependency-confusion package, even though it does not harvest credentials or execute shell commands. The concrete package-confusion behavior and telemetry justify blocking.
Decision evidence
public snapshot- package.json defines postinstall: node postinstall.js and bin mapkit-loader -> ./index.js
- postinstall.js runs at install time and sends an HTTPS POST to npx-monitor-76056.azurewebsites.net/api/pingback
- index.js sends the same pingback when invoked via npx/bin
- Both JS files create/read a persistent install identifier at $XDG_CACHE_HOME/.mapkit-loader-id or ~/.cache/.mapkit-loader-id
- README and console text state this is an npx confusion PoC for @apple/mapkit-loader
- Source does not read arbitrary files, credentials, or broad environment variables
- No child_process, eval/vm/Function, native binary loading, or destructive actions found
- Console output warns users that it is not Apple's official package
Source & flagged code
2 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to mapkit-loader@1.0.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing mapkit-loader@1.0.1. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.