Malicious Code Injection in manda-5 Package: A Threat to npm Users

manda-5 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-159648: Malicious code in manda-5 (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 manda-5 package is part of the npm ecosystem, which is widely used for managing JavaScript packages. It is designed to facilitate the development of applications by providing reusable code components. However, this package has been identified as part of a malicious campaign that floods the npm registry with harmful scripts aimed at inflating developer reputation scores through automated publishing of derivative packages.

Vulnerability Detail

The vulnerability in the manda-5 package stems from its association with the tea.xyz token reward campaign. It contains malicious scripts that modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can compromise the integrity of other packages and applications relying on npm.

How To Fix

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

npm uninstall manda-5

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 manda-5 package and replace it with a trusted alternative that provides similar functionality without the associated risks. Always verify the integrity of packages before installation.

Conclusion

The manda-5 package poses a significant threat to npm users due to its malicious code that modifies package metadata and floods the npm registry. It is crucial to remove this package and monitor your dependencies for vulnerabilities to maintain the security of your applications.

See every vulnerability recorded for manda-5 →

Share this vulnerability

FAQ

The manda-5 package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing.

The vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of other packages and applications that rely on npm.

You should uninstall the manda-5 package immediately using 'npm uninstall manda-5' and review your other dependencies for security.

No, there are no patches available for the manda-5 package as it is inherently malicious. The best course of action is to remove it from your project.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities. You can also check your application against known vulnerabilities using the Vulert playground.

How To Fix

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

npm uninstall manda-5

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