Malicious Code Injection in intan-63 Package: A Threat to npm Ecosystem
Summary
MAL-2025-156575: Malicious code in intan-63 (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-63 package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. The primary function of intan-63 is to facilitate the tea.xyz token reward campaign, which incentivizes developers to publish numerous packages, thereby inflating their reputation scores. However, this behavior poses significant risks to the integrity of the npm registry and the security of applications relying on these packages.
Vulnerability Detail
The vulnerability in the intan-63 package originates from its malicious code that 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, which pollutes the npm registry and can compromise the security of applications that depend on these packages. The malicious payload is designed to automate the creation and publication of these packages, making it difficult for developers to track and manage their dependencies effectively.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall intan-63If 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 measure, you can avoid using the intan-63 package and replace it with a trusted alternative that provides similar functionality. Always verify the integrity and reputation of packages before including them in your project.
Conclusion
The intan-63 package poses a significant threat to the npm ecosystem due to its malicious code that manipulates package metadata and floods the registry with unwanted variants. It is essential for developers to be vigilant, remove any instances of this package, and utilize tools like Vulert to monitor their projects for vulnerabilities.
See every vulnerability recorded for intan-63 →
FAQ
The intan-63 package is a malicious npm package that is part of a campaign to inflate developer reputation scores through the automatic generation and publication of derivative packages.
The vulnerability can lead to the pollution of the npm registry, making it difficult to manage dependencies and potentially introducing security risks into your application.
You should uninstall the intan-63 package immediately using the command npm uninstall intan-63 and review your project's dependencies for any other malicious packages.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities in your software.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
