Malicious Code Injection in manadsi-sdada-mivafifdida Package

manadsi-sdada-mivafifdida Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-159413: Malicious code in manadsi-sdada-mivafifdida (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 manadsi-sdada-mivafifdida package is part of the npm ecosystem and appears to be associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. Its functionality is compromised due to the presence of malicious scripts that manipulate package metadata.

Vulnerability Detail

The vulnerability originates from malicious code embedded within the manadsi-sdada-mivafifdida package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants that pollute the npm registry. The ramifications include potential security risks for developers who unknowingly use this package, as it can lead to the installation of compromised dependencies and damage to the integrity of the npm ecosystem.

How To Fix

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

npm uninstall manadsi-sdada-mivafifdida

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 workaround, avoid using the manadsi-sdada-mivafifdida package altogether. Instead, look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your dependencies using tools like Vulert, which can alert you to vulnerabilities in your package-lock.json file.

Conclusion

The manadsi-sdada-mivafifdida package contains malicious code that poses significant risks to developers and the npm ecosystem. It is crucial to remove this package from your projects and monitor your dependencies for vulnerabilities to ensure the security and integrity of your applications.

See every vulnerability recorded for manadsi-sdada-mivafifdida →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.

The malicious code can modify your package.json, remove private flags, and lead to the installation of compromised packages, posing security risks.

You should uninstall the manadsi-sdada-mivafifdida package immediately and check for any affected dependencies.

You can use Vulert to monitor your package-lock.json file for vulnerabilities in real-time without needing to access the code or install additional tools.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without signing up.

How To Fix

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

npm uninstall manadsi-sdada-mivafifdida

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