Malicious Code Injection in manda-13 Package: npm Vulnerability Overview

manda-13 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-159608: Malicious code in manda-13 (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The manda-13 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 linked to a series of malicious packages flooding the npm registry. These packages are designed to manipulate developer reputation scores by automatically generating and publishing derivative packages with randomized names.

Vulnerability Detail

The vulnerability in the manda-13 package originates from its association with malicious scripts that modify the package.json file. These scripts remove private flags, alter version numbers, and create random package names, leading to the continuous republishing of variants that pollute the npm registry. This can result in significant reputational damage for developers and potential security risks for applications relying on these packages.

How To Fix

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

npm uninstall manda-13

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, avoid using the manda-13 package and consider using alternative packages that provide similar functionality without the associated risks. Regularly audit your package dependencies to ensure they do not include any malicious packages.

Conclusion

The manda-13 package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remove this package and monitor their dependencies for similar vulnerabilities to maintain the security and integrity of their applications.

See every vulnerability recorded for manda-13 →

Share this vulnerability

FAQ

The manda-13 package is an npm package associated with the tea.xyz token reward campaign, which has been identified as containing malicious code.

The vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your application by introducing malicious code.

You should uninstall the manda-13 package immediately and check for any dependencies that may be affected.

You can use tools like 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-13

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