Malicious Code Injection in troubled_swordfish_0xrequest Package
Summary
MAL-2025-109855: Malicious code in troubled_swordfish_0xrequest (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 troubled_swordfish_0xrequest package is part of the npm ecosystem, typically used for various JavaScript functionalities. However, it has been identified as part of a malicious campaign aimed at exploiting npm's package management system. This package is associated with the tea.xyz token reward scheme, which has led to the proliferation of numerous derivative packages that compromise the integrity of the npm registry.
Vulnerability Detail
The vulnerability in the troubled_swordfish_0xrequest package stems from its malicious code that modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to clutter the npm registry. This behavior not only affects the reputation of developers but also poses a risk of dependency confusion and potential exploitation of applications relying on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall troubled_swordfish_0xrequestIf 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, consider using a package-lock.json file to lock your dependencies to specific versions and prevent the installation of this malicious package. You can also monitor your dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time without requiring code access.
Conclusion
The troubled_swordfish_0xrequest package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry with unwanted variants. It is essential to remove this package and monitor your dependencies to maintain the security and integrity of your applications.
See every vulnerability recorded for troubled_swordfish_0xrequest →
FAQ
It is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.
The vulnerability can lead to dependency confusion, potential exploitation, and damage to your application's integrity.
You should uninstall the troubled_swordfish_0xrequest package immediately and monitor your dependencies for any further vulnerabilities.
Yes, you can use Vulert to monitor your package-lock.json file and receive alerts for any open-source vulnerabilities in real-time.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.
