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

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

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

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

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

Yes — @zettle-bo/capital is associated with the GHSA-g2hg-v756-69w3, RLMA-2024-00236 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/capital 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/capital (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/capital across your stack and pipelines.

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

Malicious package

@zettle-bo/capitalnpm

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

MAL-2023-8193

Immediate action

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

npm uninstall @zettle-bo/capital

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)

0edefc32682a93278a1161ed28b71422f389e6192c800c17cd48030832f50e12

3a925afc4a054d7be777003262dbdcb36bd2f0b36dca8e9eee94faef0ff504ff

98d30d2456a1f9fb94888db4e814d509b8e09a8037d9d4b4d07bf29dca1f17d9

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/capital (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/capital across your stack and pipelines.
If you installed it — respond
Remove @zettle-bo/capital 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/capital 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/capital 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/capital 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-g2hg-v756-69w3RLMA-2024-00236

References

Credits

ReversingLabs · finder

Detect & block this

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