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/cash-registernpm

@zettle-bo/cash-register is a confirmed malicious npm package (MAL-2023-8194) 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/cash-register (npm)

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

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)

ede3f984e1ba545642d80ef08ce7649b6094423fff89e48416e59028359f2530
3b2423938517656e965b29f3d14223eaf2418fb2b83eeb66e95b5ed46aaedf95
58deab4a7b167f6c1c77f70cf689799526cae442d4bd5c6855df65d9df912429

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @zettle-bo/cash-register (version 35.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @zettle-bo/cash-register across your stack and pipelines.

  2. If you installed it — respond

    Remove @zettle-bo/cash-register 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/cash-register 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 @zettle-bo/cash-register 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. @zettle-bo/cash-register 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-g9gj-9496-j3v4RLMA-2024-00237

References

Credits

  • ReversingLabs · finder

Detect & block this

O3 blocks @zettle-bo/cash-register-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/cash-register (npm) malicious package — MAL-2023-8194 | O3 Security