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/react-spanpm

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

MAL-2023-8205
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @zettle-bo/react-spa

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)

476ca9163b9976a64e9b1596fb739c8dc2c4725cd2f321d998e6da3cf072e3ae
2e557b31cc3e3a107b4de3f5ff49138e29718416e7d8edaff7c39dbb6c8c14c3
0fde8d6d24b399941d5a4d63b260884c96671dcdfdef376730dab7a4621de43e

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

  2. If you installed it — respond

    Remove @zettle-bo/react-spa 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/react-spa 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/react-spa 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/react-spa 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-7959-6gqh-9rp6RLMA-2024-00248

References

Credits

  • ReversingLabs · finder

Detect & block this

O3 blocks @zettle-bo/react-spa-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/react-spa (npm) malicious package — MAL-2023-8205 | O3 Security