Which versions of @immuta/pxl-components are malicious?

The following npm versions of @immuta/pxl-components are flagged malicious: 99.99.0, 99.99.1. Treat any of these as compromised.

How do I remediate @immuta/pxl-components if I installed it?

@immuta/pxl-components 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.

I already installed @immuta/pxl-components — how do I know if it already compromised me?

If @immuta/pxl-components 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.

How do I find @immuta/pxl-components across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @immuta/pxl-components (2 malicious versions).

Malicious package

@immuta/pxl-componentsnpm

Advisory published Mar 13, 2026Updated Aug 25, 2026

@immuta/pxl-components is a confirmed malicious npm package (MAL-2026-1383) that steals credentials and exfiltrates sensitive data (malicious versions 99.99.0, 99.99.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @immuta/pxl-components (npm)

MAL-2026-1383

Immediate action

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

npm uninstall @immuta/pxl-components

What this malware does

Malicious package due to data exfiltration, arbitrary command execution, and suspicious install scripts targeting dependency confusion.

The package @immuta/pxl-components was found to contain malicious code.

Malicious versions

2 flagged

99.99.099.99.1

Indicators of compromise (SHA-256)

03d86f67d7f931d0f720838a4bda33d56a54a5502b29ebe3e1094a984041b7a2

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for @immuta/pxl-components (2 malicious versions).
If you installed it — respond
@immuta/pxl-components 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.
Did it already run?
If @immuta/pxl-components 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. @immuta/pxl-components on npm has been identified as a malicious package (versions 99.99.0, 99.99.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

app.safedep.io

Credits

Amazon Inspector · finder
SafeDep · finder

Detect & block this

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

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database