Malicious Code Injection in manadsi-sfda-murf: A Threat to npm Packages
Summary
MAL-2025-159449: Malicious code in manadsi-sfda-murf (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The 'manadsi-sfda-murf' package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development and distribution of JavaScript applications. However, it has been identified as part of a malicious campaign that exploits npm's publishing capabilities to inflate developer reputation scores through the automatic generation of derivative packages.
Vulnerability Detail
The vulnerability in 'manadsi-sfda-murf' originates from its association with the tea.xyz token reward campaign. This package contains scripts designed to automatically publish numerous derivative packages with randomized names, effectively polluting the npm registry. The malicious payload modifies the package.json file to remove private flags, alters version numbers, and continuously republishes variants, which can lead to reputational damage for developers and potential security risks for users who unknowingly install these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall manadsi-sfda-murfIf 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 prevent the installation of this package by using npm's package-lock.json file to monitor dependencies. Ensure that your project does not include 'manadsi-sfda-murf' in its dependencies. You can also use the following command to audit your project for vulnerabilities: npm audit.
Conclusion
The 'manadsi-sfda-murf' package poses a significant threat due to its malicious code designed to manipulate npm's publishing system. It is crucial for developers to be vigilant, remove any affected packages, and utilize monitoring tools like Vulert to safeguard their applications against such vulnerabilities.
See every vulnerability recorded for manadsi-sfda-murf →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the automatic publishing of derivative packages.
The vulnerability can lead to the installation of malicious packages that may compromise your application's security and integrity.
You should immediately remove the 'manadsi-sfda-murf' package from your project and check for any other potentially compromised packages.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can also check your application against known vulnerabilities using the Vulert playground.
Regularly audit your dependencies, keep your packages updated, and utilize tools like Vulert to monitor for vulnerabilities in real-time.
