Malicious Code Injection in improved_tick_requirement Package
Summary
MAL-2025-94967: Malicious code in improved_tick_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 improved_tick_requirement package is part of the npm ecosystem, typically used in JavaScript projects to manage dependencies. It is designed to facilitate specific functionalities related to tick requirements in applications. However, this package has been identified as part of a malicious campaign that exploits npm's publishing mechanisms, leading to potential security risks for developers and their applications.
Vulnerability Detail
The vulnerability stems from the package being associated with a malicious campaign that floods the npm registry with derivative packages. It includes scripts that modify the package.json file to remove private flags, change version numbers, and generate random package names. This behavior can lead to the pollution of the npm registry, making it difficult for developers to trust the packages they are using and potentially exposing their applications to further vulnerabilities.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall improved_tick_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 improved_tick_requirement package and look for alternative packages that provide similar functionalities without the associated risks. Always verify the integrity and reputation of packages before including them in your project.
Conclusion
The improved_tick_requirement package poses significant security risks due to its association with malicious activities in the npm ecosystem. It is essential for developers to be vigilant about the packages they use, regularly monitor for vulnerabilities, and take immediate action to remove any compromised packages.
See every vulnerability recorded for improved_tick_requirement →
FAQ
It is an npm package used in JavaScript projects, but it has been identified as part of a malicious campaign.
The vulnerability can lead to the pollution of the npm registry and may expose your application to further security risks.
You should uninstall the improved_tick_requirement package immediately and look for alternatives.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities without any signup.
