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/appsnpm

@zettle-bo/apps is a confirmed malicious npm package (MAL-2024-1767) 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/apps (npm)

MAL-2024-1767
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @zettle-bo/apps

Malicious versions

1 flagged
35.0.0

Indicators of compromise (SHA-256)

7486bb39e9a6de2b5aa73d48702c41e6a1f53c3e97fe66b86da8a25fb5890063
1b102441f681add1f0a0133b7d171661ad252cd2dfde17bccdc28b8146de2dcb
94b30644f7fa16789f73501e6bc7f563f0e5242496a70ef2c19cc06416bee76b

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/apps (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/apps across your stack and pipelines.

  2. If you installed it — respond

    Remove @zettle-bo/apps 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/apps 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/apps 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/apps 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

RLMA-2024-00233RLUA-2024-06091

References

Credits

  • ReversingLabs · finder

Detect & block this

O3 blocks @zettle-bo/apps-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/apps (npm) malicious package — MAL-2024-1767 | O3 Security