Malicious Code Injection in curious_cod-strongdev Package
Summary
MAL-2025-101146: Malicious code in curious_cod-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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The curious_cod-strongdev package is part of the npm ecosystem, typically used for various development tasks. However, it has been identified as part of a malicious campaign that aims to exploit npm's package publishing system. This package is associated with the tea.xyz token reward initiative, which has led to the proliferation of numerous derivative packages designed to inflate developer reputation scores.
Vulnerability Detail
The vulnerability in the curious_cod-strongdev package stems from its malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. The origin of this issue is linked to a broader campaign that floods the npm registry with harmful packages, potentially compromising the integrity of the ecosystem and affecting developers who rely on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall curious_cod-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 workaround, you can avoid using the curious_cod-strongdev package and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your package dependencies using tools like npm audit to identify and mitigate vulnerabilities.
Conclusion
The curious_cod-strongdev package poses a significant risk due to its malicious code that alters essential project files. It is crucial to remove this package and monitor your dependencies for vulnerabilities to maintain the integrity of your application.
See every vulnerability recorded for curious_cod-strongdev →
FAQ
curious_cod-strongdev is an npm package that has been identified as part of a malicious campaign aimed at exploiting the npm registry.
The vulnerability can lead to the modification of your package.json file, potentially causing your application to behave unexpectedly or become compromised.
You should uninstall the curious_cod-strongdev package immediately and check for any dependencies that may be affected.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
