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

@3stripes/auth Updated 15 Mar 2026

Summary

15/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1425: Malicious code in @3stripes/auth (npm). Affects @3stripes/auth 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/auth package is a Node.js library used for authentication purposes in web applications. It provides developers with tools to manage user sessions and secure access to resources. However, version 999.0.2 has been flagged for malicious behavior, which compromises its integrity and the security of applications utilizing it.

Vulnerability Detail

The vulnerability in the @3stripes/auth package arises from its communication with a domain linked to malicious activities. This behavior can lead to data breaches, unauthorized access, and potential exploitation of user credentials. The package was identified as malicious by the OpenSSF Package Analysis project, which monitors and assesses the safety of open-source packages.

How To Fix

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

npm uninstall @3stripes/auth

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 temporarily removing the @3stripes/auth package from your project until a secure version is available. This can be done using the command: npm uninstall @3stripes/auth.

Conclusion

The @3stripes/auth package version 999.0.2 has been identified as malicious due to its communication with harmful domains. It is crucial for developers to update or remove this package to safeguard their applications and user data. Utilizing tools like Vulert can help monitor for such vulnerabilities in real-time.

See every vulnerability recorded for @3stripes/auth →

Share this vulnerability

FAQ

The package communicates with a domain associated with malicious activities, posing a risk to user data and application security.

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

As a temporary measure, you can uninstall the @3stripes/auth package until a secure version is released.

The vulnerability was identified by the OpenSSF Package Analysis project, which specializes in analyzing the safety of open-source packages.

It is recommended to check the package repository for the latest stable version that does not have the malicious behavior associated with it.

How To Fix

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

npm uninstall @3stripes/auth

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