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/public-api-sdknpm

Advisory published Updated

@emilgroup/public-api-sdk is a confirmed malicious npm package (MAL-2026-2058) that steals credentials and exfiltrates sensitive data (malicious versions 1.33.1, 1.33.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @emilgroup/public-api-sdk (npm)

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

What this malware does

The package @emilgroup/public-api-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.

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.33.11.33.2

Indicators of compromise (SHA-256)

756ff891ddbf9344f303746025f56edfd29e1218410af1abb122b0e644b95458
49b32ec5041ad00c8a07401245056cc069fd80826da4c73121803ffc3a705119
53955ef666d27a04dc86d41d2c8775da967ae8cbb472454b4f5750d128a8c794

Detection & response playbook

Credential / info stealer
  1. Find it

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

  2. If you installed it — respond

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

Campaign

GHSA-qf6c-xv4h-gxw5

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @emilgroup/public-api-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/public-api-sdk (npm) malicious package — MAL-2026-2058 | O3 Security