Malicious Code Injection in ida-lapis49-sluey: A Threat to npm Ecosystem
Summary
MAL-2025-134229: Malicious code in ida-lapis49-sluey (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 package 'ida-lapis49-sluey' is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by generating and publishing numerous derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for rewards, posing a significant risk to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in 'ida-lapis49-sluey' stems from its malicious code that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. This not only pollutes the npm registry but also compromises the security of applications relying on these packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which has been associated with numerous malicious packages flooding the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall ida-lapis49-slueyIf 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 'ida-lapis49-sluey' package in your project. Additionally, consider using npm audit to identify and address vulnerabilities in your dependencies.
Conclusion
The 'ida-lapis49-sluey' package poses a significant threat due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities using tools like Vulert. Staying informed and proactive is key to maintaining the security of your applications.
See every vulnerability recorded for ida-lapis49-sluey →
FAQ
The vulnerability can lead to the pollution of the npm registry and compromise the security of applications that depend on this package.
You can use tools like Vulert to monitor your package-lock.json for vulnerabilities. Visit Vulert Scanner to check if your application is affected without any signup.
It is recommended to remove the package immediately and check for any potential security breaches in your application.
Currently, there is no specific patched version available for 'ida-lapis49-sluey'. Regularly check for updates from the package maintainers.
Vulert monitors your package-lock.json in real-time for open-source vulnerabilities, alerting you to any issues without requiring code access or installation.
