Malicious Code Vulnerability in pulseforgeasdehj Package
Summary
MAL-2025-96104: Malicious code in pulseforgeasdehj (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 pulseforgeasdehj package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is implicated in a malicious campaign that aims to inflate developer reputation scores through the creation of derivative packages. It is designed to automatically publish variants with altered metadata, making it susceptible to exploitation and misuse.
Vulnerability Detail
The vulnerability originates from the pulseforgeasdehj package, which contains malicious scripts that modify the package.json file. These modifications include removing private flags, changing version numbers, and generating random package names. This behavior leads to the continuous republishing of these variants, polluting the npm registry and potentially compromising the integrity of other packages and applications that depend on npm.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall pulseforgeasdehjIf 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 the pulseforgeasdehj package by using npm's package-lock.json file to lock your dependencies. Additionally, consider using a tool like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The pulseforgeasdehj package poses a significant risk due to its malicious behavior of modifying package metadata and republishing variants. It is crucial to remove this package from your project and monitor for vulnerabilities to ensure the security and integrity of your applications.
See every vulnerability recorded for pulseforgeasdehj →
FAQ
The pulseforgeasdehj package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the automatic generation and publication of derivative packages.
This vulnerability can compromise the integrity of your application by introducing malicious code that alters package metadata and floods the npm registry with unwanted packages.
You should uninstall the pulseforgeasdehj package immediately and check your package-lock.json file for any references to it. Consider using Vulert to monitor for vulnerabilities.
Currently, there is no patched version of the pulseforgeasdehj package available. The best course of action is to remove it from your project.
You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file. You can also check your application against known vulnerabilities using the Vulert playground.
