Malicious Code Vulnerability in personal_smelt_requirement Package
Summary
MAL-2025-95884: Malicious code in personal_smelt_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 personal_smelt_requirement package is part of the npm ecosystem, often utilized in JavaScript projects for various functionalities. However, it has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. This package, like others in the campaign, is designed to manipulate developer reputation scores through automated publishing scripts.
Vulnerability Detail
The vulnerability stems from the presence of malicious code within the personal_smelt_requirement package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which are then continuously republished. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, leading to potential security breaches and loss of integrity in their projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall personal_smelt_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 personal_smelt_requirement package and look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before including them in your project.
Conclusion
The personal_smelt_requirement package poses a significant risk due to its malicious code that alters project files and publishes unauthorized packages. It is crucial for developers to remove this package from their projects and to utilize tools like Vulert for ongoing vulnerability monitoring.
See every vulnerability recorded for personal_smelt_requirement →
FAQ
It is an npm package that has been identified as part of a malicious campaign aimed at manipulating developer reputation scores.
The malicious code modifies your package.json file, potentially leading to security vulnerabilities and the pollution of the npm registry.
You should uninstall the personal_smelt_requirement package immediately and check your project for any other compromised dependencies.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without requiring any signup.
