Malicious Code Vulnerability in indirect_crane-notthedev Package
Summary
MAL-2025-104155: Malicious code in indirect_crane-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 indirect_crane-notthedev package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores. However, it has been identified as containing malicious code that compromises the integrity of the npm registry.
Vulnerability Detail
The vulnerability originates from the package's malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants that pollute the npm registry, potentially affecting other developers and users relying on npm for package management. The malicious scripts included in the package (auto.js, autopublish.js, etc.) are designed to automate these harmful actions.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall indirect_crane-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 avoid using the indirect_crane-notthedev package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for any unauthorized changes to package.json.
Conclusion
The indirect_crane-notthedev package poses a significant risk due to its malicious code that alters package.json and pollutes the npm registry. It is crucial to remove this package from your projects and monitor for any unauthorized changes. Utilizing tools like Vulert can help maintain the security of your software.
See every vulnerability recorded for indirect_crane-notthedev →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, designed to automate the publication of derivative packages.
The malicious code modifies your package.json file, removes private flags, and can lead to the pollution of the npm registry, affecting your project's integrity.
You should uninstall the indirect_crane-notthedev package immediately and check for any dependencies that may be affected.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can check your application for vulnerabilities without signup at the Vulert playground.
Regularly audit your dependencies, use tools like Vulert for monitoring, and stay informed about known vulnerabilities in the packages you use.
