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

apple-internal-security-audit-v99npm

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

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

What this malware does

The package apple-internal-security-audit-v99 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-internal-security-audit-v99' @ 1.0.1 (npm) as malicious.

It is considered malicious because:

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

Malicious versions

2 flagged
1.0.11.0.3

Indicators of compromise (SHA-256)

1dcf86d70842a665b33fe3ea39596ce7a658051606d4b02e3f4e6e519e0d93d1
578a3a59242cce337a9e69b982333fdbe5f9236a2b6115d5b6a5bfe56a52e8ad
85c1a320034eadbc47dbe12b147164f4b003babca198b527d6b725a9f891f188
56e24d8aebeb81312fb0708469f2947c492ba2316a743d42540d28337fdaf452

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-internal-security-audit-v99 (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging apple-internal-security-audit-v99 across your stack and pipelines.

  2. If you installed it — respond

    Remove apple-internal-security-audit-v99 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-internal-security-audit-v99 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-internal-security-audit-v99 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-internal-security-audit-v99 on npm has been identified as a malicious package (versions 1.0.1, 1.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-66w7-4qx2-62w2

References

Credits

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

Detect & block this

O3 blocks apple-internal-security-audit-v99-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-internal-security-audit-v99 (npm) malicious package — MAL-2026-3305 | O3 Security