Which versions of apple-internal-config are malicious?

Every published version of apple-internal-config on npm is considered malicious. Remove the package entirely.

How do I remediate apple-internal-config if I installed it?

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.

I already installed apple-internal-config — how do I know if it already compromised me?

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.

Is apple-internal-config part of a known attack campaign?

Yes — apple-internal-config is associated with the GHSA-66g4-jx7f-f88p campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find apple-internal-config across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for apple-internal-config (all published 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.

Malicious package

apple-internal-confignpm

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

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

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

d66cace1bb3a523684936875f1283c66c30cac3d2b515829b58e24ad3ce959fc

16ae120f182e305f15d778dfe594aa3f79076b93b5bd4be77f293fdf08c5e12a

Detection & response playbook

Malicious package

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 (all published 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.
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.
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.
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 (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-66g4-jx7f-f88p

References

github.com

Credits

Amazon Inspector · 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.

Malware detection Runtime egress monitoring