Malicious Code Injection in pulseforgeasdehr Package - npm Vulnerability

pulseforgeasdehr Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-96112: Malicious code in pulseforgeasdehr (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 pulseforgeasdehr package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development of applications by providing reusable code modules. However, it has been identified as part of a malicious campaign that exploits npm's publishing system, leading to serious security concerns.

Vulnerability Detail

The vulnerability originates from the pulseforgeasdehr package being involved in a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts designed to manipulate the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior can lead to the pollution of the npm registry, potentially compromising the integrity of applications that rely on these packages. The malicious payload can also inflate developer reputation scores fraudulently, posing a risk to the broader developer community.

How To Fix

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

npm uninstall pulseforgeasdehr

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, avoid using the pulseforgeasdehr package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project's dependencies using tools like Vulert, which can alert you to open-source vulnerabilities in real-time.

Conclusion

The pulseforgeasdehr package has been identified as part of a malicious campaign that poses significant risks to applications relying on npm packages. It is crucial to remove this package and monitor your dependencies for vulnerabilities to maintain the security of your applications.

See every vulnerability recorded for pulseforgeasdehr →

Share this vulnerability

FAQ

The pulseforgeasdehr package is a JavaScript package available on npm, intended for use in application development.

This vulnerability can lead to the injection of malicious code into your application, potentially compromising its security and integrity.

If you have installed the pulseforgeasdehr package, you should uninstall it immediately and look for alternative packages.

You can use Vulert to monitor your project for vulnerabilities by analyzing your package-lock.json file. It provides real-time alerts for any open-source vulnerabilities.

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

How To Fix

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

npm uninstall pulseforgeasdehr

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