Malicious Code Injection in linguistic_shrimp_0xrequest Package
Summary
MAL-2025-105200: Malicious code in linguistic_shrimp_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 linguistic_shrimp_0xrequest package is part of the npm ecosystem, often used for various linguistic processing tasks. However, it has been identified as a component of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. This package, like others in the campaign, is designed to inflate developer reputation scores through automated publishing scripts.
Vulnerability Detail
The vulnerability originates from the package being part of a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of applications that depend on this package. The malicious payload can affect developers' reputations and the overall trustworthiness of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall linguistic_shrimp_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, you can avoid using the linguistic_shrimp_0xrequest package and look for alternative packages that provide similar functionality without the associated risks. Always verify the source and reputation of packages before including them in your project.
Conclusion
The linguistic_shrimp_0xrequest package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is essential to remove this package from your projects and to be vigilant about the packages you choose to use in the future. Utilizing tools like Vulert can help you stay informed about potential vulnerabilities.
See every vulnerability recorded for linguistic_shrimp_0xrequest →
FAQ
The package contains malicious code that modifies package.json files and floods the npm registry with derivative packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit the Vulert playground at Vulert Scanner to check your application without needing to sign up.
You should uninstall the linguistic_shrimp_0xrequest package immediately using the command npm uninstall linguistic_shrimp_0xrequest.
Yes, consider looking for other linguistic processing packages that are well-reviewed and have a good reputation in the npm ecosystem.
Regularly audit your dependencies, use tools like Vulert for monitoring, and only install packages from trusted sources.
