Malicious Code Exploit in frequent_slug_requirement Package
Summary
MAL-2025-94609: Malicious code in frequent_slug_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 frequent_slug_requirement package is part of the npm ecosystem, primarily used for generating unique slugs for web applications. However, this package has been identified as part of a malicious campaign that floods the npm registry with derivative packages, compromising its integrity and security.
Vulnerability Detail
The vulnerability stems from the package being associated with a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is designed to inflate developer reputation scores for token rewards, leading to potential pollution of the npm registry and risks of unintentional dependency on compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall frequent_slug_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 remove the frequent_slug_requirement package from your project by executing: npm uninstall frequent_slug_requirement. This will prevent any malicious code from executing while you assess alternative packages or wait for a patched version.
Conclusion
The frequent_slug_requirement package has been identified as a vector for malicious code that can compromise the integrity of applications relying on it. It is crucial to take immediate action by updating or removing the package to safeguard your project from potential threats.
See every vulnerability recorded for frequent_slug_requirement →
FAQ
frequent_slug_requirement is an npm package used for generating unique slugs for web applications, but it has been compromised by malicious actors.
The vulnerability can lead to the pollution of your npm dependencies, potentially introducing malicious code into your application.
You should immediately update the package to the latest version or remove it from your project to avoid security risks.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using your package-lock.json file. You can check for vulnerabilities without any signup at the Vulert playground.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability.
