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

google-cloud-secret-manager-config-pocnpm

google-cloud-secret-manager-config-poc is a confirmed malicious npm package (MAL-2026-3309) that steals credentials and exfiltrates sensitive data (malicious version 99.9.14). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in google-cloud-secret-manager-config-poc (npm)

MAL-2026-3309
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall google-cloud-secret-manager-config-poc

What this malware does

Malicious npm package published by the microsop threat actor as part of a dependency-confusion campaign that impersonates internal tooling at Microsoft, Google Cloud, and PayPal using inflated semver values (e.g. 99.9.x, 100.1.x) to win npm resolution against private internal packages. All packages in the campaign falsely advertise themselves as "Security Research PoC" and execute on preinstall via node index.js, exfiltrating to disposable webhook.site endpoints.

This package targets Google-Cloud-flavored internal naming and performs SSH key validation/fingerprinting on the build host. On install it checks for /root/.ssh/id_rsa, runs ssh-keygen -l -f to extract the key fingerprint and ssh-keygen -y -f to derive the public key, then POSTs {hostname, fingerprint, public_key, key_exists} to https://webhook.site/813b99f6-c86c-4a1f-9318-518a3c153992 tagged status: KEY_VALIDATION_RESULT. The captured fingerprint and public key let the operator correlate the install host against authorized-keys lists for downstream lateral movement.

The package google-cloud-secret-manager-config-poc 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 'google-cloud-secret-manager-config-poc' @ 99.9.14 (npm) as malicious.

It is considered malicious because:

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

Malicious versions

1 flagged
99.9.14

Indicators of compromise (SHA-256)

daa2f2438668b4ed2d4a869c9cd52cc3e989b235e08652eb8a041db22c222ae2
a4735e524b9623da4da209d597cdc515ed3f0cd2534591e1d98539d5b5f11f4c
78aa5b7e81cd5f702eb55e2ac9f5d3e79c1923f1d6a12f36467bcf259d440a1a

Detection & response playbook

Credential / info stealer
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for google-cloud-secret-manager-config-poc (version 99.9.14). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging google-cloud-secret-manager-config-poc across your stack and pipelines.

  2. If you installed it — respond

    google-cloud-secret-manager-config-poc 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.

  3. Did it already run?

    If google-cloud-secret-manager-config-poc 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 google-cloud-secret-manager-config-poc 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. google-cloud-secret-manager-config-poc on npm has been identified as a malicious package (version 99.9.14 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-g6v5-9xpp-6hpx

References

Credits

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

Detect & block this

O3 blocks google-cloud-secret-manager-config-poc-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

google-cloud-secret-manager-config-poc (npm) malicious package — MAL-2026-3309 | O3 Security