Critical Malicious Code Vulnerability in parashaxmgflhg Package

parashaxmgflhg Updated 19 Dec 2025

Summary

19/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192635: Malicious code in parashaxmgflhg (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 Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The parashaxmgflhg package is an npm module that is typically used for various functionalities in JavaScript applications. However, this package has been identified as containing malicious code, which poses a significant security risk to any system where it is installed. Users of this package should be aware of its potential to compromise sensitive data and system integrity.

Vulnerability Detail

The vulnerability originates from the presence of embedded malicious code within the parashaxmgflhg package. This code can lead to full compromise of any computer running the package, allowing unauthorized access to secrets and keys stored on the system. The malicious nature of this code is classified under CWE-506, indicating that it appears to be intentionally harmful. Users should consider any system with this package installed as fully compromised, and the ramifications could include data theft, unauthorized access, and further exploitation of the system.

How To Fix

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

npm uninstall parashaxmgflhg

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

There are no effective workarounds to mitigate the risks posed by this malicious package. The only recommended action is to uninstall the package and secure the system.

Conclusion

The parashaxmgflhg package has been identified as containing malicious code that compromises system security. Immediate action is required to uninstall the package and secure any sensitive information. Users are encouraged to utilize tools like Vulert for ongoing monitoring of vulnerabilities in their software.

See every vulnerability recorded for parashaxmgflhg →

Share this vulnerability

FAQ

Immediately uninstall the package using the command 'npm uninstall parashaxmgflhg' and rotate any sensitive keys or secrets stored on the affected system.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application against this vulnerability using the Vulert playground at Vulert Scanner.

Failing to remove the parashaxmgflhg package can lead to unauthorized access to your system, data theft, and potential further exploitation by malicious actors.

Regularly audit your dependencies and utilize tools like Vulert to monitor for vulnerabilities in your open-source packages.

CWE-506 indicates that the product contains code that appears to be malicious in nature, highlighting the serious security implications of the parashaxmgflhg package.

How To Fix

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

npm uninstall parashaxmgflhg

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