Malicious Code Injection in rural_eel-notthedev: A Threat to npm Users
Summary
MAL-2025-108302: Malicious code in rural_eel-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
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 package 'rural_eel-notthedev' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to manipulate npm's publishing system by generating and publishing derivative packages with randomized names. Its primary function is to inflate developer reputation scores for token rewards, but it poses significant risks due to its malicious payload.
Vulnerability Detail
The vulnerability in 'rural_eel-notthedev' originates from its inclusion in a campaign that floods the npm registry with malicious packages. The package contains scripts that modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to pollution of the npm registry, making it difficult for developers to find legitimate packages and potentially compromising their projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall rural_eel-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 measure, you can avoid using the 'rural_eel-notthedev' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your dependencies for vulnerabilities.
Conclusion
The 'rural_eel-notthedev' package poses a significant threat 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 using tools like Vulert. Staying informed and proactive can help mitigate risks associated with open-source software.
See every vulnerability recorded for rural_eel-notthedev →
FAQ
The primary risk is that it modifies your package.json file and floods the npm registry with malicious packages, which can lead to project instability and security vulnerabilities.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
If you have installed the 'rural_eel-notthedev' package, you should uninstall it immediately using 'npm uninstall rural_eel-notthedev' and look for alternatives.
Yes, tools like Vulert can monitor your package-lock.json file to alert you in real-time for open-source vulnerabilities.
Using compromised packages can lead to security breaches, data loss, and damage to your project's reputation, making it crucial to regularly audit your dependencies.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
