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

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

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

Remove @zettle-bo/routes 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/routes — how do I know if it already compromised me?

If @zettle-bo/routes 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/routes part of a known attack campaign?

Yes — @zettle-bo/routes is associated with the GHSA-g2qv-c7hp-pq3j, RLMA-2024-00250 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/routes across my projects, lockfiles, and CI pipelines?

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

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

Malicious package

@zettle-bo/routesnpm

Advisory published Sep 21, 2023Updated Oct 24, 2024

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

MAL-2023-8207

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @zettle-bo/routes

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)

5aa58a36545bf3bfb7acfdee7ca0ccfeef15bb87c3e2c31651f41e8fa9070026

852851d78e320ca244a766048e86dc389c403308121e88ee73ae97a145e97019

12b5ae2e20e528304e50342d03dbd9b1576e9c2e500871c3642d7937672aeabe

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @zettle-bo/routes (version 35.0.0).
If you installed it — respond
Remove @zettle-bo/routes 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/routes 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/routes 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-g2qv-c7hp-pq3jRLMA-2024-00250

References

Credits

ReversingLabs · finder

Detect & block this

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