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

apple-security-internal-scanner-v3npm

Malicious code in apple-security-internal-scanner-v3 (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-3188
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall apple-security-internal-scanner-v3

What this malware does

The package apple-security-internal-scanner-v3 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-security-internal-scanner-v3' @ 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)

737d706aa0ea58f3adf22752a514da4fd2017d12699d131cafd76bc1d5ccb72f
6088746661229cdf51da875e15d5ba99c4ebee26f205b968e5aa52015a80cfad
2726e7776f506696fb512788536442906d9b7348bfebf01de10af88096c42fe1

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-security-internal-scanner-v3 (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-security-internal-scanner-v3 across your stack and pipelines.

  2. If you installed it — respond

    Remove apple-security-internal-scanner-v3 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-security-internal-scanner-v3 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-security-internal-scanner-v3 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-security-internal-scanner-v3 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-fqqh-jjx6-5vcg

References

Credits

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

Detect & block this

O3 blocks apple-security-internal-scanner-v3-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-security-internal-scanner-v3 (npm) malicious package — MAL-2026-3188 | O3 Security