Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Part of a larger attack: @sev-ui-verse published 22 malicious packages. See the full campaign →
Malicious package

@sev-ui-verse/snackbarnpm

@sev-ui-verse/snackbar is a confirmed malicious npm package (MAL-2025-47546) that executes malicious code on install (malicious version 339.52.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @sev-ui-verse/snackbar (npm)

MAL-2025-47546
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @sev-ui-verse/snackbar

What this malware does

The package @sev-ui-verse/snackbar was found to contain malicious code.

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
339.52.1

Indicators of compromise (SHA-256)

f92a070917a547edd5e73a9b1b800cdd1d7e726e1886a712901dc3830d831abe
bddc2c2774f3052a229478a333c3c7b5e4b839bb1d6be643720865ee8be2b0b4
7e0c792934574f172df76758b7a0e5829ea3336382faabd5035870bed49e4987

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 @sev-ui-verse/snackbar (version 339.52.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @sev-ui-verse/snackbar across your stack and pipelines.

  2. If you installed it — respond

    Remove @sev-ui-verse/snackbar 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 @sev-ui-verse/snackbar 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 @sev-ui-verse/snackbar 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. @sev-ui-verse/snackbar on npm has been identified as a malicious package (version 339.52.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-53f9-6mpj-xj96RLMA-2025-04897RLUA-2025-05260

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks @sev-ui-verse/snackbar-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

@sev-ui-verse/snackbar (npm) malicious package — MAL-2025-47546 | O3 Security