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

manda-38 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-159635: Malicious code in manda-38 (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-38 package is part of the npm ecosystem, primarily utilized for JavaScript development. It is often involved in token reward campaigns, which can lead to the proliferation of malicious packages. This specific package has been identified as containing harmful scripts that manipulate package metadata and publish unauthorized variants, posing a significant risk to developers and users alike.

Vulnerability Detail

The vulnerability in the manda-38 package stems from its association with the tea.xyz token reward campaign. It includes scripts designed to automatically modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior not only inflates developer reputation scores but also leads to the pollution of the npm registry with potentially harmful packages. The malicious payload can compromise the integrity of projects relying on this package, leading to security breaches and loss of trust in the npm ecosystem.

How To Fix

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

npm uninstall manda-38

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 measure, you can avoid using the manda-38 package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using npm audit to identify and address vulnerabilities in your project.

Conclusion

The manda-38 package poses a significant security threat due to its malicious code that alters package metadata and publishes unauthorized variants. It is crucial for developers to remove this package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can help maintain the integrity of your software dependencies.

See every vulnerability recorded for manda-38 →

Share this vulnerability

FAQ

The manda-38 package is an npm package that has been linked to malicious activities, specifically related to token reward campaigns.

The vulnerability can lead to unauthorized modifications of your package.json file and the introduction of harmful packages into your project, compromising its security.

You should remove the manda-38 package immediately and monitor your project for any unusual behavior.

Yes, you can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time without requiring code access.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

npm uninstall manda-38

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