Malicious Code Vulnerability in back_marmot-notthedev Package
Summary
MAL-2025-99733: Malicious code in back_marmot-notthedev (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 back_marmot-notthedev 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. These packages often contain scripts that automatically generate and publish derivative packages, compromising the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in the back_marmot-notthedev package stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is designed to inflate developer reputation scores for token rewards, leading to pollution of the npm registry. The malicious payload can potentially allow unauthorized access to sensitive data and disrupt the normal functioning of applications relying on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall back_marmot-notthedevIf 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 remove the back_marmot-notthedev package from your project by executing: npm uninstall back_marmot-notthedev. Additionally, consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The back_marmot-notthedev package contains a significant vulnerability due to its malicious code that compromises the npm registry. It is crucial for developers to take immediate action by updating or removing the package to protect their applications from potential threats.
See every vulnerability recorded for back_marmot-notthedev →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the publication of derivative packages.
The vulnerability can lead to unauthorized modifications in your application's dependencies, potentially exposing sensitive data and causing disruptions.
You should immediately update or uninstall the back_marmot-notthedev package to mitigate the risks associated with this vulnerability.
Yes, tools like Vulert can monitor your package-lock.json file for open-source vulnerabilities in real-time, alerting you to any issues.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
