Malicious Code Injection in native_scallop_z3n Package
Summary
MAL-2025-106201: Malicious code in native_scallop_z3n (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 native_scallop_z3n package is part of the npm ecosystem, primarily used for JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with packages that contain malicious scripts. These scripts are designed to manipulate package metadata and inflate developer reputation scores, posing significant risks to users and the integrity of the npm registry.
Vulnerability Detail
The vulnerability in the native_scallop_z3n package stems from its inclusion in a campaign that deploys malicious code. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which leads to the continuous republishing of these variants. This behavior not only pollutes the npm registry but also compromises the security of applications that depend on this package, potentially allowing for unauthorized access and manipulation of code.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall native_scallop_z3nIf 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 native_scallop_z3n package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly monitor your package-lock.json file for any unauthorized changes.
Conclusion
The native_scallop_z3n package poses a significant security risk due to its malicious code that alters package metadata and repackages itself. It is crucial to remove this package from your projects and monitor your dependencies for any similar vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for native_scallop_z3n →
FAQ
The main issue is the presence of malicious code that modifies package metadata and repackages it, leading to potential security vulnerabilities.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit the Vulert playground at Vulert Scanner to check your application without any signup.
If you have installed the native_scallop_z3n package, you should uninstall it immediately and look for alternatives.
While specific exploits have not been detailed, the malicious behavior of the package can lead to unauthorized access and manipulation of your application.
Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay informed about vulnerabilities in the packages you use.
