Malicious Code Injection in dsilynor-notthedevs Package: A Threat to npm Users
Summary
MAL-2025-101792: Malicious code in dsilynor-notthedevs (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 dsilynor-notthedevs package is part of the npm ecosystem, primarily used for JavaScript development. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. This package, like others in the campaign, is designed to manipulate the npm registry by generating and publishing derivative packages with altered metadata, thereby inflating developer reputation scores for token rewards.
Vulnerability Detail
The vulnerability in the dsilynor-notthedevs 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 variants that pollute the npm registry. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which aims to exploit npm's publishing mechanisms for malicious purposes. The ramifications include potential security risks for developers who unknowingly use these packages, as well as a compromised npm registry that can affect the integrity of the ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall dsilynor-notthedevsIf 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, avoid using the dsilynor-notthedevs package and consider using alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file for any unauthorized changes using tools like Vulert, which alerts you to open-source vulnerabilities in real-time.
Conclusion
The dsilynor-notthedevs package poses a significant threat to npm users due to its malicious code that alters package metadata and repopulates the npm registry with compromised packages. It is essential to uninstall this package and monitor your dependencies for vulnerabilities to maintain the integrity of your projects.
See every vulnerability recorded for dsilynor-notthedevs →
FAQ
The dsilynor-notthedevs package is an npm package associated with the tea.xyz token reward campaign, known for flooding the npm registry with malicious packages.
The malicious code modifies your package.json file, potentially leading to unauthorized changes and the continuous republishing of compromised packages.
You should uninstall the dsilynor-notthedevs package immediately using the command npm uninstall dsilynor-notthedevs.
Yes, you can use Vulert, which monitors your package-lock.json file for vulnerabilities in real-time without requiring code access or installation.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by the dsilynor-notthedevs 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.
