Malicious Code Injection in interior_tiglon_requirement Package
Summary
MAL-2025-95095: Malicious code in interior_tiglon_requirement (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 interior_tiglon_requirement package is part of the npm ecosystem, primarily used for managing dependencies in JavaScript applications. This package has been identified as part of a broader malicious campaign that aims to exploit npm's publishing mechanisms. It is designed to automatically generate and publish derivative packages, which can lead to significant pollution of the npm registry and compromise the integrity of applications relying on this package.
Vulnerability Detail
The vulnerability originates from the malicious code embedded within the interior_tiglon_requirement package. This code is part of a scheme that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. The malicious payload continuously republishes these variants, which can inflate developer reputation scores fraudulently and lead to the proliferation of untrustworthy packages in the npm registry. This poses a risk to developers who may unknowingly incorporate these compromised packages into their applications, leading to potential security breaches.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall interior_tiglon_requirementIf 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 interior_tiglon_requirement package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities.
Conclusion
The interior_tiglon_requirement package poses a significant security risk due to its malicious code designed to exploit npm's publishing system. It is crucial for developers to remove this package from their projects and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for interior_tiglon_requirement →
FAQ
It is an npm package that has been identified as part of a malicious campaign aimed at exploiting npm's publishing mechanisms.
If your application relies on the interior_tiglon_requirement package, it may be at risk of incorporating malicious code that can compromise its security.
You should uninstall the interior_tiglon_requirement package immediately and check for any other affected packages in your project.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software by analyzing the package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
