Malicious Code Injection in associated_limpet_requirement Package
Summary
MAL-2025-93295: Malicious code in associated_limpet_requirement (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 associated_limpet_requirement package is part of the npm ecosystem, typically used for managing dependencies in JavaScript applications. This package has been identified as part of a malicious campaign that aims to exploit npm's publishing system. It is designed to automatically generate and publish derivative packages with altered metadata to inflate developer reputation scores for token rewards.
Vulnerability Detail
The vulnerability originates from the malicious nature of the associated_limpet_requirement package, which includes scripts that modify the package.json file to remove private flags, change version numbers, and generate random package names. This behavior leads to the continuous republishing of variants that pollute the npm registry, potentially compromising the integrity of the ecosystem and affecting developers who rely on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall associated_limpet_requirementIf 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 workaround, you can monitor your project's dependencies using tools like Vulert, which can alert you to open-source vulnerabilities in real-time. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The associated_limpet_requirement package poses a significant risk due to its malicious behavior, which can compromise the npm ecosystem. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity of their applications.
See every vulnerability recorded for associated_limpet_requirement →
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 the pollution of the npm registry and may compromise the integrity of your project's dependencies.
You should uninstall the associated_limpet_requirement package immediately and monitor your dependencies for any further vulnerabilities.
Currently, there is no patched version available. The best course of action is to remove the package.
You can use tools like Vulert, which allows you to monitor and alert for open-source vulnerabilities using just your package-lock.json file.
