Malicious Code Injection in statistical_sloth-excellentdev Package

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-109091: Malicious code in statistical_sloth-excellentdev (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 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 statistical_sloth-excellentdev package is part of the npm ecosystem, typically used for statistical analysis and data manipulation. However, this package has been identified as part of a malicious campaign that exploits npm's publishing capabilities. The vulnerability stems from the package's involvement in generating and publishing derivative packages with random names, aimed at inflating developer reputation scores for token rewards.

Vulnerability Detail

This vulnerability originates from the package being part of the tea.xyz token reward campaign, which has been flooding the npm registry with malicious packages. The malicious code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior can lead to the pollution of the npm registry and may compromise the integrity of other packages, potentially allowing for further exploitation.

How To Fix

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

npm uninstall statistical_sloth-excellentdev

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, you can avoid using the statistical_sloth-excellentdev package and replace it with a trusted alternative for your statistical analysis needs. Always verify the integrity of packages before installation.

Conclusion

The statistical_sloth-excellentdev package has been identified as a vector for malicious code injection, posing significant risks to applications using it. It is crucial to remove this package and monitor your dependencies regularly to maintain the security of your software.

See every vulnerability recorded for statistical_sloth-excellentdev →

Share this vulnerability

FAQ

It is an npm package used for statistical analysis, but it has been compromised with malicious code.

The vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your application by introducing malicious code.

You should uninstall the statistical_sloth-excellentdev package immediately and replace it with a trusted alternative.

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

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.

How To Fix

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

npm uninstall statistical_sloth-excellentdev

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