Malicious Code Exploit in active_snake_white-91: A Threat to npm Packages

active_snake_white-91 Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-99099: Malicious code in active_snake_white-91 (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 Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The package 'active_snake_white-91' is part of a series of npm packages that have been associated with the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior not only compromises the integrity of the npm registry but also poses a significant risk to developers relying on these packages for their applications.

Vulnerability Detail

The vulnerability originates from the malicious code embedded within the 'active_snake_white-91' package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants. The ramifications include pollution of the npm registry, potential security risks for applications using these packages, and exploitation of developer reputation systems. The malicious payload is designed to operate stealthily, making it difficult for developers to detect its presence.

How To Fix

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

npm uninstall active_snake_white-91

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 avoid using the 'active_snake_white-91' package and replace it with a trusted alternative. Always review the packages you include in your project for any signs of malicious behavior.

Conclusion

The 'active_snake_white-91' package poses a significant threat due to its malicious code designed to manipulate npm package publishing. It is crucial for developers to remain vigilant, regularly update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. Taking immediate action to remove this package can help safeguard your application from potential risks.

See every vulnerability recorded for active_snake_white-91 →

Share this vulnerability

FAQ

It is an npm package associated with a malicious campaign that inflates developer reputation scores through automated publishing of derivative packages.

The malicious code modifies your package.json file and can lead to the pollution of the npm registry, potentially compromising your application's security.

You should uninstall the 'active_snake_white-91' package immediately and review your project's dependencies for any other potentially harmful packages.

You can use tools like Vulert, which monitors and alerts you in real-time for open-source vulnerabilities using just your package-lock.json file.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

How To Fix

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

npm uninstall active_snake_white-91

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