Malicious Code Injection in pulseforgeasdehi: A Threat to npm Ecosystem
Summary
MAL-2025-96103: Malicious code in pulseforgeasdehi (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 package 'pulseforgeasdehi' is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. These malicious packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores, posing a significant risk to developers and users relying on the integrity of npm packages.
Vulnerability Detail
The vulnerability in 'pulseforgeasdehi' stems from its association 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 intended to pollute the npm registry and can lead to the unintentional installation of compromised packages by developers. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which incentivizes the creation of such malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall pulseforgeasdehiIf 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 'pulseforgeasdehi' package and any other packages that are part of the malicious campaign. Regularly audit your npm packages using the command 'npm audit' to identify and address vulnerabilities.
Conclusion
The 'pulseforgeasdehi' package poses a significant threat to the npm ecosystem due to its malicious behavior aimed at manipulating package metadata and polluting the registry. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to safeguard their applications against such vulnerabilities.
See every vulnerability recorded for pulseforgeasdehi →
FAQ
The vulnerability can lead to the installation of compromised packages, which may alter your project's dependencies and introduce security risks.
You can use the Vulert platform to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.
There is no patch for the 'pulseforgeasdehi' package itself. The recommended action is to uninstall the package and remove any dependencies associated with it.
Regularly audit your npm packages, keep dependencies updated, and utilize tools like Vulert to monitor for vulnerabilities in real-time.
Immediately uninstall the 'pulseforgeasdehi' package using 'npm uninstall pulseforgeasdehi' and review your project's dependencies for any other potentially malicious packages.
