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

clementine-sdknpm

Malicious code in clementine-sdk (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-3822
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall clementine-sdk

What this malware does

The package clementine-sdk 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 'clementine-sdk' @ 2.0.0 (npm) as malicious.

It is considered malicious because:

  • The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged
2.0.0

Indicators of compromise (SHA-256)

a70cc29cff5e0ec61fc3eb66c8921f4dfd4e7a8275cdffa4a8708be9195531a2
aee6ab0f050d475e499cb88539f229969e72affe6313b116693e5da3fa7c7a4c
24a589617ff547a464cb26e7d9a5675151e221ab5d144088fbc60cb0fbe41135

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

  2. If you installed it — respond

    Remove clementine-sdk 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 clementine-sdk 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 clementine-sdk 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. clementine-sdk on npm has been identified as a malicious package (version 2.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-fc9m-mqj9-8j3r

References

Credits

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

Detect & block this

O3 blocks clementine-sdk-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.

clementine-sdk (npm) malicious package — MAL-2026-3822 | O3 Security