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

clover-codelab-remote-pay-cloudnpm

clover-codelab-remote-pay-cloud is a confirmed malicious npm package (MAL-2026-12353) that steals credentials and exfiltrates sensitive data (malicious version 99.9.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in clover-codelab-remote-pay-cloud (npm)

MAL-2026-12353
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall clover-codelab-remote-pay-cloud

What this malware does

The package declares a postinstall hook that runs index.js on npm install. index.js collects the OS username, current working directory, hostname, and non-internal IPv4 address via os.userInfo(), process.cwd(), os.hostname(), and os.networkInterfaces(), then POSTs the values as JSON over https to a hardcoded webhook.site collector at https://webhook.site/9aa13631-fbb0-4b6b-a256-27d1672f767c. The package name resembles Clover's remote-pay-cloud SDK and the version is set to 99.9.9, a dependency-confusion shape intended to override an internal package during resolution. The package provides no functionality matching its name — its only install-time effect is the exfiltration beacon.

Malicious versions

1 flagged
99.9.9

Indicators of compromise (SHA-256)

071fbdd6b5ca7cbb0fc696f5abf7a47be3783dd970ca5594cb415e67579f2b15

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 clover-codelab-remote-pay-cloud (version 99.9.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging clover-codelab-remote-pay-cloud across your stack and pipelines.

  2. If you installed it — respond

    clover-codelab-remote-pay-cloud 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 clover-codelab-remote-pay-cloud 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 clover-codelab-remote-pay-cloud 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. clover-codelab-remote-pay-cloud on npm has been identified as a malicious package (version 99.9.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014866

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks clover-codelab-remote-pay-cloud-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

Explore

All malware advisories How O3 detects malware Vulnerability database
clover-codelab-remote-pay-cloud (npm) malicious package — MAL-2026-12353 | O3 Security