Malicious Code Detected in phx-core4 Package - Security Alert

phx-core4 Updated 19 Mar 2026

Summary

18/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1813: Malicious code in phx-core4 (npm). Affects phx-core4 versions 8.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 Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

phx-core4 is an npm package designed for core functionalities in web applications. It is widely used due to its modular design and ease of integration with various frameworks. However, recent findings have revealed that this package is vulnerable to malicious code injection, which can compromise the security of applications relying on it.

Vulnerability Detail

The vulnerability in phx-core4 stems from the inclusion of malicious code that can execute unauthorized actions within the application environment. This issue was identified in version 8.0.0 and poses significant risks, including data breaches, unauthorized access, and potential system compromise. The malicious code was reported by ReversingLabs, highlighting the importance of scrutinizing package dependencies for security threats.

How To Fix

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

npm uninstall phx-core4

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 measure, consider removing the phx-core4 package from your project until a secure version is confirmed. You can uninstall it using the command: npm uninstall phx-core4.

Conclusion

The discovery of malicious code in the phx-core4 package underscores the importance of maintaining secure dependencies in software projects. By updating to a patched version or removing the package, developers can protect their applications from potential threats.

See every vulnerability recorded for phx-core4 →

Share this vulnerability

FAQ

The vulnerability involves malicious code that can execute unauthorized actions within applications using the phx-core4 package.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

The risks include data breaches, unauthorized access to sensitive information, and potential system compromise, which can lead to severe operational disruptions.

Yes, it is recommended to update the phx-core4 package to the latest secure version to mitigate the risks associated with this vulnerability.

If immediate updates are not possible, consider removing the package from your project as a temporary workaround until a secure version is available.

How To Fix

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

npm uninstall phx-core4

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