Malicious Code Injection in remarkable_scallop_requirement Package
Summary
MAL-2025-96289: Malicious code in remarkable_scallop_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 remarkable_scallop_requirement package is part of the npm ecosystem, primarily used in JavaScript applications. It is designed to facilitate certain functionalities within projects but has been compromised. This package has been linked to a broader malicious campaign that aims to exploit npm's package management system, leading to potential security risks for developers and their applications.
Vulnerability Detail
The vulnerability originates from a malicious campaign associated with the tea.xyz token reward initiative. The remarkable_scallop_requirement package contains scripts that automatically generate and publish derivative packages with altered names and configurations. This behavior not only inflates developer reputation scores but also modifies the package.json file to remove private flags and change version numbers. The continuous republishing of these variants pollutes the npm registry, posing significant risks to users who may unknowingly install these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall remarkable_scallop_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 temporary workaround, you can avoid using the remarkable_scallop_requirement package until a secure version is released. Additionally, consider using alternative packages that provide similar functionalities without the associated risks.
Conclusion
The remarkable_scallop_requirement package has been identified as a vector for malicious code injection, posing significant risks to applications using it. Developers are advised to update or remove the package and utilize tools like Vulert for ongoing monitoring of vulnerabilities in their dependencies.
See every vulnerability recorded for remarkable_scallop_requirement →
FAQ
It is an npm package used in JavaScript applications, but it has been compromised and is part of a malicious campaign.
If your application uses this package, it may be exposed to malicious scripts that can alter your package configurations and compromise your security.
You should update the package to a patched version or remove it from your project until a secure version is available.
You can use tools like Vulert, which monitors and alerts you in real-time for open-source vulnerabilities in your software by analyzing your package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
