Malicious Code Injection in pulseforgeasdeho: A Threat to npm Ecosystem

pulseforgeasdeho Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-96109: Malicious code in pulseforgeasdeho (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The package pulseforgeasdeho is part of the npm ecosystem, which is widely used for managing JavaScript packages. It is often utilized in various applications to streamline development processes. However, this package has been identified as part of a malicious campaign that aims to exploit npm's publishing capabilities, leading to potential security risks for developers and users alike.

Vulnerability Detail

The vulnerability in pulseforgeasdeho originates from its association with a token reward campaign that floods the npm registry with malicious packages. These packages contain scripts designed to automatically generate and publish derivative packages with randomized names, which can inflate developer reputation scores. The malicious payload modifies the package.json file to remove private flags, alters version numbers, and continuously republishes variants, thereby polluting the npm registry and potentially compromising the integrity of dependent applications.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall pulseforgeasdeho

If 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 pulseforgeasdeho package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools 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 pulseforgeasdeho package poses a significant security risk due to its malicious code injection capabilities. It is essential for developers to take immediate action by removing the package and monitoring their applications for vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your projects.

See every vulnerability recorded for pulseforgeasdeho →

Share this vulnerability

FAQ

pulseforgeasdeho is an npm package that has been identified as part of a malicious campaign targeting the npm ecosystem.

The vulnerability can lead to the injection of malicious code, which may compromise the security and integrity of your application.

You should uninstall the package immediately using 'npm uninstall pulseforgeasdeho' and monitor your project for any further vulnerabilities.

Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay updated with the latest security advisories.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by vulnerabilities without requiring any installation.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall pulseforgeasdeho

If 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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback