Malicious Code Injection in manda-28 Package: A Threat to npm Ecosystem

manda-28 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-159624: Malicious code in manda-28 (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-28 package is part of the npm ecosystem, which is widely used for managing JavaScript packages. It is often utilized in various applications for its functionality in handling dependencies. However, this package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages that inflate developer reputation scores for token rewards.

Vulnerability Detail

The vulnerability in the manda-28 package stems from its association with the tea.xyz token reward campaign. The package contains malicious scripts designed to 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 other packages.

How To Fix

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

npm uninstall manda-28

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-28 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-28 package poses a significant risk to the npm ecosystem due to its malicious behavior. It is crucial for developers to be aware of this vulnerability, take immediate action to remove the affected package, and monitor their applications for potential threats. Utilizing tools like Vulert can help maintain the security of your projects.

See every vulnerability recorded for manda-28 →

Share this vulnerability

FAQ

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

The vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of other packages and affecting the security of your application.

You should uninstall the manda-28 package immediately and check for any dependencies that may rely on it. Replace it with secure alternatives.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just the package-lock.json file. You can also check your application against known vulnerabilities using the Vulert playground.

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-28

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