Malicious Code Injection in intimate_lynx_dumbs Package - npm Vulnerability
Summary
MAL-2025-104366: Malicious code in intimate_lynx_dumbs (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 intimate_lynx_dumbs package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant pollution of the npm registry and compromise the integrity of the ecosystem.
Vulnerability Detail
The vulnerability in the intimate_lynx_dumbs package originates from its association with the tea.xyz token reward campaign. It contains malicious scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior not only affects the affected package but also leads to the proliferation of numerous derivative packages in the npm registry, potentially impacting developers and users relying on legitimate packages. The malicious payload can compromise the security of applications that depend on this package, leading to unauthorized access or data breaches.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall intimate_lynx_dumbsIf 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 workaround, you can temporarily avoid using the intimate_lynx_dumbs package by removing it from your dependencies. If you need similar functionality, consider using alternative packages that are known to be secure and well-maintained.
Conclusion
The intimate_lynx_dumbs package poses a significant risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for intimate_lynx_dumbs →
FAQ
The intimate_lynx_dumbs package is an npm package that has been identified as part of a malicious campaign aimed at flooding the npm registry with derivative packages.
This vulnerability can lead to the proliferation of malicious packages in your application, potentially compromising its security and integrity.
You should remove the intimate_lynx_dumbs package from your project and monitor for any updates or patches that may be released.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities in your software.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring 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.
