Malicious Code Detected in @3stripes/common Package - Version 999.0.2

@3stripes/common Updated 15 Mar 2026

Summary

15/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1426: Malicious code in @3stripes/common (npm). Affects @3stripes/common 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 Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The @3stripes/common package is an npm library designed for common functionalities used across various applications. It is intended to streamline development by providing reusable code components. However, version 999.0.2 has been flagged for malicious behavior, specifically for communicating with domains linked to malicious activities, posing a significant risk to users and their applications.

Vulnerability Detail

The vulnerability in the @3stripes/common package arises from its version 999.0.2, which has been identified as malicious by the OpenSSF Package Analysis project. This version is known to communicate with a domain associated with malicious activities, potentially leading to data breaches, unauthorized access, or other security incidents. Users of this package are at risk of exposing sensitive information or compromising their systems due to this malicious behavior.

How To Fix

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

npm uninstall @3stripes/common

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 workaround, consider removing the @3stripes/common package from your project until a secure version is released. You can do this by executing the following command: npm uninstall @3stripes/common. Additionally, monitor your application for any unusual activity that may arise from using this package.

Conclusion

The @3stripes/common package version 999.0.2 has been identified as malicious, posing significant risks to users. It is essential to take immediate action by removing the affected version and monitoring for updates. Utilizing tools like Vulert can help in identifying vulnerabilities in your application.

See every vulnerability recorded for @3stripes/common →

Share this vulnerability

FAQ

The package version 999.0.2 communicates with a domain linked to malicious activities, which could lead to security vulnerabilities.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without needing to sign up.

It is recommended to uninstall the affected version and replace it with a secure alternative or an earlier version that does not exhibit malicious behavior.

Currently, there is no patched version available for the @3stripes/common package. Users should monitor for updates from the package maintainers.

Using the malicious version can lead to data breaches, unauthorized access to sensitive information, and other security incidents that could compromise your application.

How To Fix

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

npm uninstall @3stripes/common

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