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

manda-19 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-159614: Malicious code in manda-19 (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-19 package is part of the npm ecosystem, which is widely used for JavaScript package management. It is often utilized in various applications for its functionalities, but it has been identified as part of a malicious campaign that aims to exploit npm's publishing system. This package is associated with the tea.xyz token reward scheme, which has led to the proliferation of numerous derivative packages that can compromise the integrity of the npm registry.

Vulnerability Detail

The vulnerability in the manda-19 package stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is designed to inflate developer reputation scores for token rewards, leading to the continuous republishing of variants that pollute the npm registry. The origin of this vulnerability is linked to a broader campaign that utilizes autopublish scripts to automate the creation of these harmful packages, posing significant risks to developers relying on npm for package management.

How To Fix

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

npm uninstall manda-19

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-19 package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your package dependencies for vulnerabilities.

Conclusion

The manda-19 package poses a significant threat to npm users due to its malicious code designed to exploit the npm registry. It is crucial for developers to be vigilant, regularly monitor their dependencies, and take immediate action to remove any affected packages. Utilizing tools like Vulert can help in maintaining the security of your applications.

See every vulnerability recorded for manda-19 →

Share this vulnerability

FAQ

The manda-19 package is an npm package that has been identified as part of a malicious campaign aimed at exploiting the npm registry.

The vulnerability can lead to the modification of your package.json file, potentially compromising the integrity of your application and leading to the publication of malicious variants.

You should uninstall the manda-19 package immediately and check for any other malicious packages in your project.

You can use Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.

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 manda-19

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