Malicious Code Vulnerability in explicit_marlin-biggestdev Package
Summary
MAL-2025-102404: Malicious code in explicit_marlin-biggestdev (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 explicit_marlin-biggestdev package is part of a broader ecosystem within the npm registry, often associated with token reward campaigns. These packages are designed to automate the generation and publication of derivative packages, which can inflate developer reputation scores. However, this functionality has been exploited to introduce malicious code that compromises the integrity of the npm registry.
Vulnerability Detail
The vulnerability originates from the package being part of a malicious campaign that floods the npm registry with derivative packages. The malicious code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This results in the continuous republishing of variants that pollute the npm registry, potentially leading to security risks for developers and users relying on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall explicit_marlin-biggestdevIf 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 prevent the installation of this malicious package by using npm's package-lock.json to monitor dependencies. Ensure that your project does not include explicit_marlin-biggestdev in its dependencies. You can also use Vulert to monitor your project for vulnerabilities by checking your package-lock.json file.
Conclusion
The explicit_marlin-biggestdev package poses a significant security risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to remove this package from their projects and utilize tools like Vulert to monitor for vulnerabilities effectively.
See every vulnerability recorded for explicit_marlin-biggestdev →
FAQ
It is a package in the npm registry that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing.
The vulnerability can lead to the introduction of malicious code into your project, potentially compromising its security and integrity.
You should immediately uninstall the explicit_marlin-biggestdev package from your project to mitigate any risks associated with its malicious code.
Currently, there is no patched version available for the explicit_marlin-biggestdev package. The best course of action is to remove it from your project.
Vulert can monitor your project for open-source vulnerabilities in real-time using just your package-lock.json file, alerting you to any issues without requiring code access or installation.
