Malicious Code Injection in intan-31: A Threat to npm Ecosystem
Summary
MAL-2025-156540: Malicious code in intan-31 (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
intan-31 is a package within the npm ecosystem that has been implicated in a malicious campaign targeting developers. This package is part of a broader scheme involving the tea.xyz token reward initiative, which aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious nature of intan-31 lies in its ability to manipulate package metadata and flood the npm registry with harmful variants.
Vulnerability Detail
The vulnerability in intan-31 originates from its design to execute autopublish scripts that alter the package.json file. This includes removing private flags, changing version numbers, and generating random package names, which can lead to significant pollution of the npm registry. The ramifications of this vulnerability include compromised developer reputations, potential security risks for applications relying on these packages, and a cluttered npm ecosystem that makes it difficult for legitimate packages to be discovered.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall intan-31If 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 intan-31 package and any packages that depend on it. Regularly audit your package-lock.json file for any signs of malicious packages and remove them promptly.
Conclusion
The intan-31 package poses a significant threat to the npm ecosystem due to its malicious behavior of altering package metadata and flooding the registry with harmful variants. It is crucial for developers to remain vigilant, uninstall affected packages, and utilize monitoring tools like Vulert to safeguard their projects.
See every vulnerability recorded for intan-31 →
FAQ
intan-31 is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the automatic generation of derivative packages.
The intan-31 package can modify your project's package.json file, leading to the removal of private flags and the introduction of potentially harmful variants into the npm registry.
You should uninstall intan-31 immediately using the command npm uninstall intan-31 and check for any dependencies that may rely on it.
You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time. You can also check your application against known vulnerabilities using the Vulert playground.
Regularly audit your dependencies, use tools like Vulert for monitoring, and stay updated on security advisories related to the packages you use.
