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

manda-16 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-159611: Malicious code in manda-16 (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 manda-16 package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development of applications by providing reusable code. However, it has been identified as part of a malicious campaign that exploits npm's publishing capabilities to inflate developer reputation scores through the automatic generation of derivative packages.

Vulnerability Detail

The vulnerability in the manda-16 package originates 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 applications relying on these packages. The malicious payload is designed to operate without user consent, posing significant risks to developers and users alike.

How To Fix

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

npm uninstall manda-16

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-16 package and instead rely on alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before including them in your project.

Conclusion

The manda-16 package poses a significant security risk due to its malicious code injection capabilities. It is crucial for developers to be aware of such vulnerabilities and take proactive steps to secure their applications by removing affected packages and monitoring for potential threats.

See every vulnerability recorded for manda-16 →

Share this vulnerability

FAQ

The manda-16 package is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through automated publishing.

The vulnerability can lead to the injection of malicious code into your application, potentially compromising its security and integrity.

You should uninstall the manda-16 package immediately using the command npm uninstall manda-16 and check for any other affected packages.

You can use tools like Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software. You can check your application against known vulnerabilities using the Vulert playground without any signup.

Yes, consider using other reputable packages that provide similar functionality without the associated risks. Always research and verify the packages you choose.

How To Fix

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

npm uninstall manda-16

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