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

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

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

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

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

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

Yes — @zettle-bo/settings is associated with the GHSA-jhqm-x4p5-jf46, RLMA-2024-00252 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/settings across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @zettle-bo/settings (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/settings across your stack and pipelines.

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

Malicious package

@zettle-bo/settingsnpm

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

MAL-2023-8209

Immediate action

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

npm uninstall @zettle-bo/settings

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)

fba492d667a05fc7319b7f2a8b78d3c30055af809eb17047766ddd8e1b747898

815828de94c6ab7d603cb874f821e7bc75ff27af834f70be1ebe0037f502fdd2

3fd09db93c3cf4527188a4627b2b634f753b5f19a0500a840553e29dcc38cb5c

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @zettle-bo/settings (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/settings across your stack and pipelines.
If you installed it — respond
Remove @zettle-bo/settings 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/settings 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.
How O3 protects you
O3 blocks @zettle-bo/settings 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/settings 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-jhqm-x4p5-jf46RLMA-2024-00252

References

Credits

ReversingLabs · finder

Detect & block this

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