Malicious Code Injection in pulseforgeasdehq: A Threat to npm Ecosystem
Summary
MAL-2025-96111: Malicious code in pulseforgeasdehq (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 'pulseforgeasdehq' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is linked to the tea.xyz token reward campaign, notorious for flooding the npm registry with malicious packages. These packages are designed to inflate developer reputation scores through the automatic generation and publication of derivative packages with randomized names.
Vulnerability Detail
The vulnerability in 'pulseforgeasdehq' stems from its malicious payload that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, potentially leading to security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall pulseforgeasdehqIf 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, avoid using the 'pulseforgeasdehq' package and consider using alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your dependencies using tools like npm audit to identify and address vulnerabilities.
Conclusion
The 'pulseforgeasdehq' package poses a significant risk due to its malicious code that manipulates package.json and floods the npm registry. It is crucial for developers to remove this package and monitor their dependencies to maintain the security of their applications.
See every vulnerability recorded for pulseforgeasdehq →
FAQ
The main issue is that it contains malicious code that modifies package.json and floods the npm registry with harmful variants.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.
You should uninstall the package immediately using 'npm uninstall pulseforgeasdehq' and check your package-lock.json for any remaining references.
Yes, consider looking for other npm packages that provide similar functionality without the associated risks. Always verify the credibility of the packages you choose.
Regularly audit your dependencies using tools like npm audit, and stay informed about vulnerabilities in the packages you use.
