Malicious Code Injection in intan-17 Package: npm Vulnerability Summary
Summary
MAL-2025-156525: Malicious code in intan-17 (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-17 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 for token rewards. However, it has been identified as containing malicious code that compromises its integrity and the integrity of the npm registry.
Vulnerability Detail
The vulnerability originates from the malicious design of the intan-17 package, which includes scripts that modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially harming developers who rely on the integrity of packages from this ecosystem. The malicious payload can also lead to unauthorized access to sensitive data and compromise the security of applications that depend on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall intan-17
If 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 intan-17 package from your project by executing the following command: npm uninstall intan-17. This will help mitigate the risk until a secure version is released.
Conclusion
The intan-17 package has been identified as containing malicious code that poses significant risks to applications relying on it. It is crucial for developers to take immediate action by updating or removing the package to ensure the security of their projects. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in real-time.
See every vulnerability recorded for intan-17 →
FAQ
The intan-17 package is an npm package associated with the tea.xyz token reward campaign, designed to automate the generation and publication of derivative packages.
The vulnerability can lead to unauthorized modifications in your package.json file, potentially compromising your application's security and integrity.
If you are using intan-17, you should update to a patched version if available or remove the package from your project to mitigate risks.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file. You can check if your application is affected by visiting the Vulert playground.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without requiring a signup.