Malicious Code Injection in specified_tiglon_requirement Package
Summary
MAL-2025-96713: Malicious code in specified_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 specified_tiglon_requirement package is part of the npm ecosystem, typically used for managing dependencies in JavaScript applications. This package has been identified as part of a malicious campaign that aims to exploit npm's publishing system. It is designed to automatically generate and publish derivative packages, which can lead to reputation inflation for the associated token reward program.
Vulnerability Detail
The vulnerability originates from the malicious code embedded within the specified_tiglon_requirement package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The continuous republishing of these variants pollutes the npm registry, potentially leading to security risks for developers who unknowingly use these compromised packages. The malicious payload can compromise the integrity of applications relying on this package, making them susceptible to further attacks.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall specified_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 specified_tiglon_requirement package altogether. If it is a dependency of another package, consider using an alternative package that does not have known vulnerabilities. Additionally, you can use the following command to uninstall the package: npm uninstall specified_tiglon_requirement.
Conclusion
The specified_tiglon_requirement package poses a significant risk due to its malicious code that alters package configurations and pollutes the npm registry. It is essential to remove this package from your projects and monitor for any dependencies that may be affected. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for specified_tiglon_requirement →
FAQ
It is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.
The vulnerability can compromise your application's integrity by introducing malicious code, which may lead to further security risks.
You should uninstall the specified_tiglon_requirement package immediately and check for any dependencies that may rely on it.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without requiring any signup.
