Critical Malicious Code Vulnerability in phx-core Package

phx-core Updated 15 Dec 2025

Summary

15/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192572: Malicious code in phx-core (npm). Affects phx-core versions 9.0.0. 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 phx-core package is a library used in Node.js applications, providing essential functionalities for developers. It is widely utilized in various projects due to its ease of integration and robust features. However, recent findings have revealed a significant vulnerability that compromises the security of systems using this package, making it imperative for users to be aware and take action.

Vulnerability Detail

The vulnerability identified in the phx-core package is classified as malicious code embedded within the software. Originating from a malicious source, this code can fully compromise any computer that has the package installed. The ramifications include unauthorized access to sensitive information, such as secrets and keys, stored on the affected system. Users are advised to treat any system running this package as compromised, as the malicious code may persist even after removal of the package.

How To Fix

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

npm uninstall phx-core

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

Currently, there are no specific workarounds to mitigate the effects of this vulnerability other than removing the package and securing the system.

Conclusion

The discovery of malicious code in the phx-core package poses a serious threat to users and their systems. Immediate action is required to remove the package and secure any sensitive information. Users are encouraged to stay informed about updates and potential patches for this vulnerability.

See every vulnerability recorded for phx-core →

Share this vulnerability

FAQ

You should remove the phx-core package immediately and rotate any secrets or keys stored on the affected system.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

As of now, there is no specific patch available. Users are advised to remove the package until a safe version is released.

Failing to address this vulnerability can lead to unauthorized access to sensitive data and potential control of your system by malicious actors.

Vulert monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file, providing real-time insights without requiring code access.

How To Fix

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

npm uninstall phx-core

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