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/auth-sdk-nodenpm

Advisory published Updated

@emilgroup/auth-sdk-node is a confirmed malicious npm package (MAL-2026-2037) that steals credentials and exfiltrates sensitive data (malicious versions 1.21.1, 1.21.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @emilgroup/auth-sdk-node (npm)

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

What this malware does

Analysis of @emilgroup/[email protected] produced no a static rule matches and no traced install-time or import-time behaviors indicating credential theft, exfiltration, remote code execution, silent-relay, backdoor, or dependency-chain dropper patterns. No attacker-controlled network destinations, no lifecycle hooks fetching external code, and no reads of installer secret paths were observed.

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.

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

2 flagged
1.21.11.21.2

Indicators of compromise (SHA-256)

9e1e171ea3809a2a4defc33338d7c733b582525ff73609fcea0ea374d8c22210
ccb489120e1ad55e75b6bacdf15a54015c9de9959ea853cd391dc4dd66948001
fe2626034ff9db4050961980269d01868886c3b537585d5e9bf6fb31eba94fd5
09c56c23b02f1954f6fd0f033441afa845f31772436b9cc5423a79ba629fccba
2e8dcb430d280d1703454bd4625bdf9bad9e11dae236d82eaa625ff8716eef0a
6a73f392d8069826ca24f969685455934ffb89d238c7ba4498b8a64818221441
eb97d9a2d10d2c28d1f0bef4d81cc0d9c2649e94df11e9620f442d7d503d89c3

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for @emilgroup/auth-sdk-node (2 malicious versions).

  2. If you installed it — respond

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

Campaign

GHSA-8328-7r2v-2fq6IN-MAL-2026-013352IN-MAL-2026-013351IN-MAL-2026-013342IN-MAL-2026-013350

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @emilgroup/auth-sdk-node-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/auth-sdk-node (npm) malicious package — MAL-2026-2037 | O3 Security