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

@emilgroup/partner-sdknpm

Malicious code in @emilgroup/partner-sdk (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-2205
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @emilgroup/partner-sdk

What this malware does

The package @emilgroup/partner-sdk was found to contain malicious code.

This package was compromised by the CanisterWorm campaign by the TeamPCP threat actor. The malicious payload establishes persistence as user systemd service and places a backdoor on the infected host. The malware will also harvest npm credentials and can autonomously spread.

Malicious versions

3 flagged
1.19.11.19.21.19.3

Indicators of compromise (SHA-256)

07ce4dc4bcadafb459b0b8e9c843204eaaa6db794788c72c45a03bd28efd5a3f
6b0abde6a2a005b2c63f18e87169a3b47ddfe6fb943ad82a005e1d3d3a8e5887

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

  2. If you installed it — respond

    @emilgroup/partner-sdk 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 @emilgroup/partner-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 @emilgroup/partner-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. @emilgroup/partner-sdk on npm has been identified as a malicious package (versions 1.19.1, 1.19.2, 1.19.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @emilgroup/partner-sdk-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.