Malicious Code Injection in maximum_tick-notthedev Package
Summary
MAL-2025-105678: Malicious code in maximum_tick-notthedev (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 maximum_tick-notthedev package is part of the npm ecosystem, primarily used for JavaScript applications. It is designed to facilitate various functionalities within the npm environment. However, this package has been identified as part of a malicious campaign that floods the npm registry with derivative packages, which can lead to significant security risks for developers and their applications.
Vulnerability Detail
The vulnerability in the maximum_tick-notthedev package originates from its association with the tea.xyz token reward campaign. This campaign has led to the creation of packages that contain scripts designed to automatically publish derivative packages with randomized names. The malicious payload modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which can lead to the pollution of the npm registry and compromise the integrity of applications relying on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall maximum_tick-notthedevIf 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 maximum_tick-notthedev package from your project by executing the command: 'npm uninstall maximum_tick-notthedev'. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The maximum_tick-notthedev package has been identified as containing malicious code that can compromise the security of applications using it. It is crucial to take immediate action by updating or removing the package to mitigate potential risks.
See every vulnerability recorded for maximum_tick-notthedev →
FAQ
It is an npm package used in JavaScript applications, but it has been compromised with malicious code.
The vulnerability can lead to the pollution of the npm registry and may compromise the security and integrity of your application.
You should update the package to a patched version or uninstall it until a secure version is released.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.
