Malicious Code Injection in intan-41 Package: A Threat to npm Ecosystem
Summary
MAL-2025-156551: Malicious code in intan-41 (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 intan-41 package is part of the npm ecosystem, which is widely used for managing JavaScript packages. This package, like many others, is intended to facilitate the development and deployment of applications by providing reusable code. However, it has been identified as part of a malicious campaign that exploits npm's publishing mechanisms to inflate developer reputation scores through the creation of derivative packages.
Vulnerability Detail
The vulnerability in the intan-41 package originates from its association with the tea.xyz token reward campaign. This package contains scripts designed to automatically generate and publish numerous derivative packages with randomized names. The malicious payload modifies the package.json file by removing private flags, altering version numbers, and continuously republishing variants, which can lead to pollution of the npm registry and compromise the integrity of the ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall intan-41If 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 the intan-41 package by using npm's package-lock.json to monitor dependencies. Ensure that you do not include this package in your project and regularly audit your dependencies for any malicious packages.
Conclusion
The intan-41 package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package publishing. It is crucial for developers to remain vigilant, audit their dependencies, and utilize tools like Vulert to ensure the security of their applications.
See every vulnerability recorded for intan-41 →
FAQ
The intan-41 package is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.
The vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of your application's dependencies and exposing it to further security risks.
You should immediately remove the intan-41 package from your project and check for any other potentially malicious packages in your dependencies.
Yes, you can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
