Malicious Code Detected in @3stripes/ui: npm Package Vulnerability

@3stripes/ui Updated 15 Mar 2026

Summary

15/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1429: Malicious code in @3stripes/ui (npm). Affects @3stripes/ui versions 999.0.2. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The @3stripes/ui package is a component library designed for building user interfaces in web applications. It provides a collection of reusable UI components that enhance the development process. However, version 999.0.2 of this package has been identified as malicious, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the @3stripes/ui package arises from its communication with a domain associated with malicious activity. This behavior can lead to unauthorized data access, potential data breaches, and compromise of the integrity of applications using this package. The malicious nature of the package was identified by the OpenSSF Package Analysis project, which flagged it based on its suspicious network activity.

How To Fix

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

npm uninstall @3stripes/ui

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

If immediate updating is not feasible, consider removing the @3stripes/ui package from your project and replacing it with an alternative UI component library that does not exhibit malicious behavior. This can be done by uninstalling the package with the command: npm uninstall @3stripes/ui.

Conclusion

The @3stripes/ui package version 999.0.2 has been flagged as malicious due to its communication with a harmful domain. It is crucial for developers to update or replace this package to safeguard their applications from potential security threats.

See every vulnerability recorded for @3stripes/ui →

Share this vulnerability

FAQ

The package has been found to communicate with a domain linked to malicious activities, which can compromise application security.

You can use Vulert, which monitors open-source vulnerabilities in your software. By analyzing your package-lock.json file, Vulert provides real-time alerts for vulnerabilities.

If you cannot update the package right away, consider removing it and using a different UI library until a safe version is available.

The vulnerability was identified by the OpenSSF Package Analysis project, which monitors and analyzes packages for malicious behavior.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by vulnerabilities without needing to sign up.

How To Fix

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

npm uninstall @3stripes/ui

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