Malicious Code Detected in Independent Loon Dumbs Package: npm Vulnerability Overview
Summary
MAL-2025-104153: Malicious code in independent_loon_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
Background
The 'independent_loon_dumbs' package is part of a broader campaign associated with the tea.xyz token reward system, which has been known to flood the npm ecosystem with malicious packages. This package is designed to manipulate npm's publishing system, potentially affecting developers' reputations and the integrity of the npm registry.
Vulnerability Detail
The vulnerability originates from the package's design, which includes autopublish scripts that automatically generate and publish derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for rewards associated with the tea protocol. The malicious payload modifies the package.json file to remove private flags, alters version numbers, and continuously republishes variants, leading to pollution of the npm registry and potential security risks for users relying on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall independent_loon_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 temporary measure, you can avoid using the 'independent_loon_dumbs' package until a secure version is released. Additionally, consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The 'independent_loon_dumbs' package poses significant risks due to its malicious code designed to manipulate npm's publishing system. It is crucial for developers to stay informed about such vulnerabilities and take necessary actions to protect their applications.
See every vulnerability recorded for independent_loon_dumbs →
FAQ
The vulnerability involves malicious code that alters package metadata and floods the npm registry with derivative packages, potentially harming developers' reputations.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without needing to sign up.
Using this package can lead to security risks, including the potential for your application to be associated with malicious activities and the pollution of the npm registry.
You should check the npm registry for any patched versions of the package. If available, updating to the latest version is recommended.
As a workaround, consider removing the package from your project and using alternative packages until a secure version is released.
