Malicious Code Detected in stats-engine Package - Security Alert

stats-engine Updated 03 Dec 2025

Summary

03/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192258: Malicious code in stats-engine (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 stats-engine package is a Node.js library commonly used in various applications for statistical analysis and data processing. It provides functionalities that allow developers to easily integrate statistical computations into their projects. However, recent findings have revealed that this package contains malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the stats-engine package originates from the inclusion of malicious code that can compromise the integrity and security of applications using this package. This code may allow unauthorized access to sensitive data, execute arbitrary commands, or lead to further exploitation of the system. The malicious code was identified by Amazon Inspector, highlighting the importance of scrutinizing third-party packages for security vulnerabilities.

How To Fix

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

npm uninstall stats-engine

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 remove the stats-engine package from your project until a secure version is available. You can do this by executing the following command: npm uninstall stats-engine. Consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The discovery of malicious code in the stats-engine package underscores the importance of regularly monitoring and updating third-party libraries. By following the recommended steps to update or remove the package, developers can protect their applications from potential security threats.

See every vulnerability recorded for stats-engine →

Share this vulnerability

FAQ

The stats-engine package is a Node.js library used for statistical analysis and data processing in applications.

The malicious code found in the stats-engine package can compromise application security, allowing unauthorized access and potential exploitation.

You can use the Vulert platform to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without any signup.

If you cannot update the package right away, consider removing it from your project and using alternative packages until a secure version is released.

The vulnerability was identified by Amazon Inspector, a tool that helps detect security issues in software packages.

How To Fix

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

npm uninstall stats-engine

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