Malicious Code Injection in complete_tick-strongdev Package
Summary
MAL-2025-100770: Malicious code in complete_tick-strongdev (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 complete_tick-strongdev package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate development by providing reusable code components. However, it has been identified as part of a malicious campaign that exploits npm's publishing capabilities, leading to potential security risks for developers who inadvertently use it.
Vulnerability Detail
The vulnerability stems from the complete_tick-strongdev package being associated with a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts designed to modify package.json files, removing private flags and altering version numbers. This behavior can lead to the unintentional exposure of sensitive information and the proliferation of untrusted packages in the npm ecosystem, ultimately compromising the integrity of applications that depend on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall complete_tick-strongdevIf 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 complete_tick-strongdev package and replace it with a similar, trusted package that does not exhibit malicious behavior. Always review the source and reputation of packages before including them in your project.
Conclusion
The complete_tick-strongdev package poses a significant security risk due to its malicious code injection capabilities. Developers should take immediate action to remove this package and ensure their applications are secure by using trusted dependencies. Regular monitoring and updates are essential to maintain the integrity of your software.
See every vulnerability recorded for complete_tick-strongdev →
FAQ
It is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.
Using this package can lead to the exposure of sensitive information and the introduction of untrusted code into your application.
You should uninstall the package immediately and review your project's dependencies for any other potentially malicious packages.
You can use tools like Vulert, which monitors your package-lock.json for 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 signing up.
