Which versions of apple-infra-gcp-leak are malicious?

The following npm versions of apple-infra-gcp-leak are flagged malicious: 1.2.0. Treat any of these as compromised.

How do I remediate apple-infra-gcp-leak if I installed it?

apple-infra-gcp-leak is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed apple-infra-gcp-leak — how do I know if it already compromised me?

If apple-infra-gcp-leak 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-infra-gcp-leak part of a known attack campaign?

Yes — apple-infra-gcp-leak is associated with the GHSA-wvgf-2hjr-hcw7 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-infra-gcp-leak 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-infra-gcp-leak (version 1.2.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging apple-infra-gcp-leak across your stack and pipelines.

Malicious package

apple-infra-gcp-leaknpm

Malicious code in apple-infra-gcp-leak (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-3154

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall apple-infra-gcp-leak

What this malware does

Malicious npm package published by threat actor "raya4321" as part of a coordinated typosquatting campaign impersonating Apple internal infrastructure services (authentication, PKI, telemetry, CloudKit, and cloud infrastructure). All packages in this campaign execute credential-theft payloads during npm installation via preinstall or postinstall lifecycle hooks.

Trigger: preinstall. Queries the GCP instance metadata service to steal the GCP project ID, zone, service account OAuth2 access token (the 'golden ticket'), and service account scopes; exfiltrates all data to https://webhook.site/1324ffab-98a9-4f19-8f72-4bbaad684aaf. The package also bundles pwn.sh, which hunts for npm/GitHub authentication tokens (NPM_TOKEN, NODE_AUTH_TOKEN, GITHUB_TOKEN, NPM_AUTH_TOKEN) in the environment and ~/.npmrc, then uses any found token to publish a trojanized version of apple-app-store-server-library to the npm registry (supply chain attack), and exfiltrates results to https://webhook.site/85f78e76-dc73-4cb5-a65c-27f2c10db591.

The package apple-infra-gcp-leak 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

1 flagged

1.2.0

Indicators of compromise (SHA-256)

78e8c1e0510900d5269d9d79d11cad804cc69d38cd2230d3c4fdef470136ee3b

fb432d919ca836694a5ccb2d4e9db7310a0300fea05231071362cc8b7a749764

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for apple-infra-gcp-leak (version 1.2.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging apple-infra-gcp-leak across your stack and pipelines.
If you installed it — respond
apple-infra-gcp-leak is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If apple-infra-gcp-leak 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-infra-gcp-leak 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-infra-gcp-leak on npm has been identified as a malicious package (version 1.2.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-wvgf-2hjr-hcw7

References

github.com

Credits

Amazon Inspector · finder
SafeDep · finder

Detect & block this

O3 blocks apple-infra-gcp-leak-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring