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

apple-internal-confignpm

apple-internal-config is a confirmed malicious npm package (MAL-2026-3168) that executes malicious code on install (malicious versions 99.9.9, 99.10.0, 100.0.1…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in apple-internal-config (npm)

MAL-2026-3168
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall apple-internal-config

What this malware does

The package apple-internal-config 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.

Malicious versions

16 flagged
99.9.999.10.0100.0.1100.0.2100.0.6100.0.7100.0.8100.0.9100.1.1100.1.2100.2.7100.3.2100.3.3100.3.5100.5.0100.6.0

Indicators of compromise (SHA-256)

d66cace1bb3a523684936875f1283c66c30cac3d2b515829b58e24ad3ce959fc
16ae120f182e305f15d778dfe594aa3f79076b93b5bd4be77f293fdf08c5e12a
a705340a674a51f9cb1f677cce716b5431077d8db6389c210c12539a7c3608fe

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-config (16 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-config across your stack and pipelines.

  2. If you installed it — respond

    Remove apple-internal-config 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-config 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-config 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-config on npm has been identified as a malicious package (versions 99.9.9, 99.10.0, 100.0.1, 100.0.2, 100.0.6, 100.0.7, 100.0.8, 100.0.9, and 8 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-66g4-jx7f-f88pRLMA-2026-04935

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks apple-internal-config-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.

Explore

apple-internal-config (npm) malicious package — MAL-2026-3168 | O3 Security