NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

@pypestream/floating-ui-domnpm

Advisory published Updated

@pypestream/floating-ui-dom is a confirmed malicious npm package (MAL-2026-2030) that steals credentials and exfiltrates sensitive data (malicious version 2.15.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @pypestream/floating-ui-dom (npm)

MAL-2026-2030
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @pypestream/floating-ui-dom

What this malware does

The package @pypestream/floating-ui-dom 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.

This package was compromised by the CanisterWorm campaign by the TeamPCP threat actor. The malicious payload establishes persistence as user systemd service and places a backdoor on the infected host. The malware will also harvest npm credentials and can autonomously spread.

Malicious versions

1 flagged
2.15.1

Indicators of compromise (SHA-256)

4707deb04498cce7bf16b61d141bc29a85f4fbadbadd75fdc3b78fdac6eb8f74
c054f1bdbe451e796bb0623296f4240c654e72b4ef794089dad3428bfed98fd2
d1300a555b6dde611d8a92485ea11ef46ab88055717da827625a8bc3421cf81a

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for @pypestream/floating-ui-dom (version 2.15.1).

  2. If you installed it — respond

    @pypestream/floating-ui-dom is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

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

Campaign

GHSA-5h9j-3cr5-f9xj

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @pypestream/floating-ui-dom-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

@pypestream/floating-ui-dom (npm) malicious package — MAL-2026-2030 | O3 Security