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

apple-appstore-full-library-utilitynpm

Malicious code in apple-appstore-full-library-utility (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-3187
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall apple-appstore-full-library-utility

What this malware does

The package apple-appstore-full-library-utility was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

The OpenSSF Package Analysis project identified 'apple-appstore-full-library-utility' @ 1.0.0 (npm) as malicious.

It is considered malicious because:

  • The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

e30e21f285d3e7ea7f24b25e246be29b030d7e9a06d1db9f6141d7b6ce6141be
7c81abc0b0ca85dceebddbddb78e6e2d6d05f87331f11b9a1190ad29d10adb4a
37d9ef929b0386b8979a06c265164e16dc41aa93289b93b7e1414dc2560bee92

Detection & response playbook

Malicious package
  1. Find it

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

  2. If you installed it — respond

    Remove apple-appstore-full-library-utility from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

    If apple-appstore-full-library-utility 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 apple-appstore-full-library-utility 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. apple-appstore-full-library-utility on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-jqp6-fcpv-q663

References

Credits

  • Amazon Inspector · finder
  • OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks apple-appstore-full-library-utility-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

apple-appstore-full-library-utility (npm) malicious package — MAL-2026-3187 | O3 Security