Malicious Code Injection in dylanmurphy Package: npm Vulnerability Overview
Summary
MAL-2025-171120: Malicious code in dylanmurphy (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 dylanmurphy package is part of the npm ecosystem, primarily used for JavaScript development. It has gained attention due to its involvement in the tea.xyz token reward campaign, which has led to the proliferation of malicious packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, making them a significant risk for developers using npm.
Vulnerability Detail
The vulnerability in the dylanmurphy package stems from its malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which aims to manipulate the npm registry and developer reputation scores. The ramifications include potential pollution of the npm registry and risks to developers who may unknowingly use these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall dylanmurphyIf 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 dylanmurphy package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can use npm audit to check for vulnerabilities in your project.
Conclusion
The dylanmurphy package poses a significant risk due to its malicious code designed to manipulate the npm registry. Developers should take immediate action to remove this package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your open-source dependencies.
See every vulnerability recorded for dylanmurphy →
FAQ
The dylanmurphy package is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through automated publishing.
You can use tools like Vulert to monitor your package-lock.json file for vulnerabilities. Vulert provides real-time alerts for open-source vulnerabilities without requiring code access.
If you have installed the dylanmurphy package, you should uninstall it immediately using 'npm uninstall dylanmurphy' and check for any dependencies that may be affected.
Yes, you should look for alternative packages that offer similar functionality but do not have the associated risks. Always verify the credibility of the packages you choose.
To prevent future vulnerabilities, regularly audit your dependencies using tools like npm audit and Vulert, and stay updated on security advisories related to the packages you use.
