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

manda-39 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-159636: Malicious code in manda-39 (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The manda-39 package is part of the npm ecosystem, primarily used for JavaScript development. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores through automated publishing of derivative packages.

Vulnerability Detail

The vulnerability in the manda-39 package originates from its association with malicious scripts that modify the package.json file. These scripts remove private flags, alter version numbers, and generate random package names, leading to the continuous republishing of variants. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly install these compromised packages, potentially leading to further exploitation.

How To Fix

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

npm uninstall manda-39

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-39 package and look for alternative packages that provide similar functionality without the associated risks. Always validate the source and integrity of packages before installation.

Conclusion

The manda-39 package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is essential for developers to be vigilant, regularly update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities in their projects.

See every vulnerability recorded for manda-39 →

Share this vulnerability

FAQ

The manda-39 package is an npm package associated with the tea.xyz token reward campaign, known for containing malicious code that modifies package metadata.

The vulnerability can lead to the installation of compromised packages, which may alter your project's dependencies and potentially expose it to further security risks.

You can use Vulert, a tool that monitors and alerts for open-source vulnerabilities in real-time. By analyzing your package-lock.json file, Vulert can help identify if your application is affected by this vulnerability.

If you have installed the manda-39 package, you should uninstall it immediately using the command: npm uninstall manda-39, and review your project's dependencies for any other potential vulnerabilities.

Yes, Vulert provides a playground where you can check if your application is affected by vulnerabilities without requiring any signup. Visit Vulert Scanner to use this feature.

How To Fix

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

npm uninstall manda-39

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