Critical Security Flaw in @immuta/pxl-components: Malicious Code Exposed

@immuta/pxl-components Updated 14 Mar 2026

Summary

13/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1383: Malicious code in @immuta/pxl-components (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The @immuta/pxl-components package is a component library designed for building user interfaces in JavaScript applications. It provides a set of reusable UI components that enhance development efficiency. However, this package has been identified as malicious, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the @immuta/pxl-components package. This code is capable of data exfiltration, arbitrary command execution, and includes suspicious install scripts that target dependency confusion. The malicious nature of this package can lead to unauthorized access to sensitive data and potential compromise of the host system.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall @immuta/pxl-components

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary measure, you can remove the @immuta/pxl-components package from your project until a secure version is confirmed. Use the following command to uninstall the package: npm uninstall @immuta/pxl-components.

Conclusion

The @immuta/pxl-components package has been identified as malicious, leading to potential data breaches and system compromises. It is crucial to update or remove this package to safeguard your applications. Utilize tools like Vulert for ongoing monitoring of vulnerabilities in your dependencies.

See every vulnerability recorded for @immuta/pxl-components →

Share this vulnerability

FAQ

The malicious code is designed for data exfiltration and arbitrary command execution, posing serious security risks.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

If an immediate update is not possible, consider uninstalling the package as a temporary workaround to mitigate risks.

Detailed information can be found in the vulnerability report at the Open Source Vulnerability database.

Yes, Vulert can monitor and alert you in real-time for open-source vulnerabilities using just your package-lock.json file.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall @immuta/pxl-components

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback