Malicious Code Injection in manadi-scaisor-didadfr Package

manadi-scaisor-didadfr Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-159328: Malicious code in manadi-scaisor-didadfr (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 manadi-scaisor-didadfr package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. Its primary functionality is to facilitate the automatic generation and publication of derivative packages, but it has been compromised to include malicious code that alters package metadata.

Vulnerability Detail

The vulnerability in the manadi-scaisor-didadfr package originates from its association with a malicious campaign that aims to inflate developer reputation scores for token rewards. The malicious code modifies the package.json file by removing private flags, changing version numbers, and generating random package names. This leads to the continuous republishing of these variants, polluting the npm registry and potentially compromising other projects that rely on these packages.

How To Fix

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

npm uninstall manadi-scaisor-didadfr

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 manadi-scaisor-didadfr package and look for alternative packages that provide similar functionality without the associated risks.

Conclusion

The manadi-scaisor-didadfr package has been identified as containing malicious code that can compromise projects using it. It is crucial to uninstall this package and monitor for any vulnerabilities in your dependencies to maintain the security of your applications.

See every vulnerability recorded for manadi-scaisor-didadfr →

Share this vulnerability

FAQ

It is an npm package that has been compromised to include malicious code as part of a token reward campaign.

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

You should uninstall the manadi-scaisor-didadfr package immediately and check for any other affected packages in your project.

Yes, 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 for vulnerabilities in your application without any signup.

How To Fix

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

npm uninstall manadi-scaisor-didadfr

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