Which versions of @zettle-bo/apps are malicious?

The following npm versions of @zettle-bo/apps are flagged malicious: 35.0.0. Treat any of these as compromised.

How do I remediate @zettle-bo/apps if I installed it?

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.

I already installed @zettle-bo/apps — how do I know if it already compromised me?

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

Is @zettle-bo/apps part of a known attack campaign?

Yes — @zettle-bo/apps is associated with the RLMA-2024-00233, RLUA-2024-06091, RLUA-2026-10660 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @zettle-bo/apps across my projects, lockfiles, and CI pipelines?

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

Part of a larger attack: @zettle-bo published 25 malicious packages. See the full campaign →

Malicious package

@zettle-bo/appsnpm

Advisory published Jun 25, 2024Updated Sep 24, 2026

@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

67282e7924d478380b04bc0c431c0f112d3b5dd396717343a915a7862bb73f11

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @zettle-bo/apps (version 35.0.0).
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.
Did it already run?
If @zettle-bo/apps 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/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-06091RLUA-2026-10660

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database