Malicious Code Injection in near_tick_requirement Package
Summary
MAL-2025-95608: Malicious code in near_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 near_tick_requirement package is part of the npm ecosystem, primarily used for managing dependencies in JavaScript applications. It is designed to facilitate the development process by providing essential functionalities. However, this package has been identified as part of a malicious campaign that floods the npm registry with harmful scripts aimed at manipulating developer reputation scores.
Vulnerability Detail
The vulnerability stems from the malicious code embedded in the near_tick_requirement package, which is linked to the tea.xyz token reward campaign. 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 leads to pollution of the npm registry, potentially affecting developers' projects and reputations.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall near_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 measure, you can avoid using the near_tick_requirement package until a secure version is released. Additionally, consider using alternative packages that provide similar functionalities without the associated risks.
Conclusion
The near_tick_requirement package has been identified as containing malicious code that poses significant risks to developers and their projects. It is essential to take immediate action by updating or removing the package and utilizing tools like Vulert for ongoing monitoring of vulnerabilities.
See every vulnerability recorded for near_tick_requirement →
FAQ
The near_tick_requirement package is an npm package used for managing dependencies in JavaScript applications, but it has been compromised with malicious code.
The malicious code modifies your package.json file, potentially leading to unauthorized changes and pollution of the npm registry, which can harm your project's integrity.
If you have installed the near_tick_requirement package, you should immediately update it to the latest patched version or remove it from your project.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
