Malicious Code Injection in pulseforgeasdehl Package
Summary
MAL-2025-96106: Malicious code in pulseforgeasdehl (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 pulseforgeasdehl package 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 packages are designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant issues in the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in the pulseforgeasdehl package stems from its association with a malicious campaign that modifies the package.json file to remove private flags and changes version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to a loss of trust in the npm ecosystem and potential security risks for developers who inadvertently use these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall pulseforgeasdehlIf 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 pulseforgeasdehl package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your package dependencies for vulnerabilities.
Conclusion
The pulseforgeasdehl package poses a significant risk due to its malicious code injection and automated publishing behavior. It is crucial for developers to remove this package from their projects and monitor their dependencies for vulnerabilities to maintain the integrity of their applications.
See every vulnerability recorded for pulseforgeasdehl →
FAQ
The pulseforgeasdehl package is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.
The vulnerability can lead to the introduction of malicious code into your project, potentially compromising its security and integrity.
You should uninstall the pulseforgeasdehl package immediately and check for any dependencies that may be affected.
You can use Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
