Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

com.apple.unityplugin.storekitnpm

com.apple.unityplugin.storekit is a confirmed malicious npm package (MAL-2026-16477) that opens a backdoor for remote access (malicious version 1.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in com.apple.unityplugin.storekit (npm)

MAL-2026-16477
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall com.apple.unityplugin.storekit

What this malware does

The package impersonates an Apple/Unity StoreKit internal namespace (com.apple.unityplugin.storekit) and, on require(), index.js performs an HTTPS GET to a hardcoded Project Discovery Interactsh (oast.fun) subdomain, transmitting the package name, os.platform(), and os.hostname() as query parameters (target: https://dapnhid534ch06s9vpm0mbg1httu5gytc.oast.fun). The behavior is unconditional, undocumented, and fires at module load with no caller opt-in. The name/scope, the author claim of 'Apple, Inc', and the OAST callback destination are the standard dependency-confusion reconnaissance shape: the beacon confirms that an internal build system has resolved the attacker's public package instead of Apple's private one, and leaks the internal hostname of the machine that resolved it.

Malicious versions

1 flagged
1.0.2

Indicators of compromise (SHA-256)

920277566757bdc38563c7e2150e906790478cbd7a0c48f0bb53004e82eec4ca

Detection & response playbook

Backdoor / remote access

  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for com.apple.unityplugin.storekit (version 1.0.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging com.apple.unityplugin.storekit across your stack and pipelines.

  2. If you installed it — respond

    com.apple.unityplugin.storekit establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

  3. Did it already run?

    If com.apple.unityplugin.storekit was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

  4. How O3 protects you

    O3 blocks com.apple.unityplugin.storekit before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. com.apple.unityplugin.storekit on npm has been identified as a malicious package (version 1.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020491

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks com.apple.unityplugin.storekit-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database
com.apple.unityplugin.storekit (npm) malicious package — MAL-2026-16477 | O3 Security