Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Part of a larger attack: @zettle-bo published 25 malicious packages. See the full campaign →
Malicious package

@zettle-bo/shellnpm

Advisory published Updated

@zettle-bo/shell is a confirmed malicious npm package (MAL-2023-8210) that executes malicious code on install (malicious version 35.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @zettle-bo/shell (npm)

MAL-2023-8210
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @zettle-bo/shell

What this malware does

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.

Malicious versions

1 flagged
35.0.0

Indicators of compromise (SHA-256)

1cb00dc072140e917d264fbf48cb87d56628674e7f6207a92f7bd7b72bde9780
a569cd197e90f80479c29bbc339bb36ed443e10d263bc7ec686d5e9cf59f58be
396e53a7065547a58232e0425d739bb0f54e063d040cec3efc89a0bf125199e5

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for @zettle-bo/shell (version 35.0.0).

  2. If you installed it — respond

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

Campaign

GHSA-m9cq-wq8c-vq32RLMA-2024-00253

References

Credits

  • ReversingLabs · finder

Detect & block this

O3 blocks @zettle-bo/shell-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.

Explore

@zettle-bo/shell (npm) malicious package — MAL-2023-8210 | O3 Security