NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Part of a larger attack: @emilgroup published 45 malicious packages. See the full campaign →
Malicious package

@emilgroup/commission-sdknpm

Advisory published Updated

@emilgroup/commission-sdk is a confirmed malicious npm package (MAL-2026-2202) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.1, 1.0.2, 1.0.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @emilgroup/commission-sdk (npm)

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

What this malware does

The package @emilgroup/commission-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.0.11.0.21.0.3

Indicators of compromise (SHA-256)

0747507ecb5327b6cd870cff26e8ef8ed455330e757b920c725988c9d36b7b7d
88cda98ba417752b6bf4aef7eb0ecf7410017226165423202ca4d5886f370478

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for @emilgroup/commission-sdk (3 malicious versions).

  2. If you installed it — respond

    @emilgroup/commission-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/commission-sdk was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @emilgroup/commission-sdk on npm has been identified as a malicious package (versions 1.0.1, 1.0.2, 1.0.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/commission-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.

Explore

@emilgroup/commission-sdk (npm) malicious package — MAL-2026-2202 | O3 Security