Critical Vulnerability in ninjaonsteroids: Malicious Code Injection

ninjaonsteroids Updated 02 Oct 2025

Summary

31/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6640: Malicious code in ninjaonsteroids (npm). Affects ninjaonsteroids versions 1.0.1 – 1.0.9. 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 'ninjaonsteroids' package is an npm library designed for enhancing JavaScript applications with various functionalities. It is widely used in the development community for its ease of integration and robust features. However, recent findings have revealed that this package contains malicious code that could compromise the security of applications utilizing it.

Vulnerability Detail

The vulnerability stems from malicious code embedded within versions 1.0.1 to 1.0.32 of the 'ninjaonsteroids' package. This code can execute harmful actions, potentially leading to data breaches or unauthorized access to sensitive information. The issue was identified by ReversingLabs, highlighting the importance of scrutinizing third-party packages for security risks.

How To Fix

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

npm uninstall ninjaonsteroids

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 removing the package temporarily from your project until a secure version is available. You can do this by executing: 'npm uninstall ninjaonsteroids'. This will help mitigate the risk while you assess alternative packages or wait for a patch.

Conclusion

The discovery of malicious code in the 'ninjaonsteroids' package underscores the importance of vigilance when using third-party libraries. By updating to a secure version or temporarily removing the package, developers can protect their applications from potential threats.

See every vulnerability recorded for ninjaonsteroids →

Share this vulnerability

FAQ

The vulnerability involves malicious code that can execute harmful actions within applications using the package.

You can use Vulert, which monitors vulnerabilities in open-source packages. By analyzing your package-lock.json file, it can alert you to any issues. Visit Vulert Scanner to check your application without signing up.

Versions 1.0.1 to 1.0.32 of the ninjaonsteroids package are known to contain the malicious code.

Yes, updating to version 1.0.0 or any version above 1.0.32 will resolve the vulnerability.

Consider uninstalling the package temporarily to mitigate risks until a secure version is available.

How To Fix

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

npm uninstall ninjaonsteroids

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