Malicious Code Injection in pulseforgeasdehn: A Threat to npm Users
Summary
MAL-2025-96108: Malicious code in pulseforgeasdehn (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 'pulseforgeasdehn' is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by generating and publishing numerous derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for token rewards, making the package a potential threat to users and the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in 'pulseforgeasdehn' originates from its malicious design, which includes scripts that modify the package.json file to remove private flags, alter version numbers, and create random package names. This results in the continuous republishing of variants that pollute the npm registry, potentially leading to security risks for developers who unknowingly install these compromised packages. The malicious payload can compromise the integrity of applications relying on this package, leading to unauthorized access or data manipulation.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall pulseforgeasdehnIf 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 remove the 'pulseforgeasdehn' package from your project by executing the following command: npm uninstall pulseforgeasdehn. Additionally, consider using alternative packages that do not have known vulnerabilities.
Conclusion
The 'pulseforgeasdehn' package poses a significant risk due to its malicious code designed to manipulate the npm registry. Users are urged to take immediate action by updating or removing the package to safeguard their applications. Utilizing tools like Vulert can help in monitoring and preventing future vulnerabilities.
See every vulnerability recorded for pulseforgeasdehn →
FAQ
The vulnerability can lead to the installation of malicious packages that may compromise application security and integrity.
You can use the Vulert service, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.
If you cannot update the package, it is advisable to remove it from your project and look for safer alternatives.
The malicious code can modify your package.json, leading to unauthorized package republishing and potential security breaches.
Regularly audit your dependencies and utilize tools like Vulert to monitor for vulnerabilities in your open-source packages.
