Which versions of phx-core4 are malicious?

The following npm versions of phx-core4 are flagged malicious: 8.0.0. Treat any of these as compromised.

How do I remediate phx-core4 if I installed it?

Remove phx-core4 from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed phx-core4 — how do I know if it already compromised me?

If phx-core4 was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is phx-core4 part of a known attack campaign?

Yes — phx-core4 is associated with the RLMA-2026-01486 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find phx-core4 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for phx-core4 (version 8.0.0).

Malicious package

phx-core4npm

Advisory published Mar 18, 2026Updated Mar 23, 2026

phx-core4 is a confirmed malicious npm package (MAL-2026-1813) that executes malicious code on install (malicious version 8.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in phx-core4 (npm)

MAL-2026-1813

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall phx-core4

What this malware does

The package phx-core4 was found to contain malicious code.

Malicious versions

1 flagged

8.0.0

Indicators of compromise (SHA-256)

a7792525eddb2edeb42a184bbd641478683a9e9d14468afa4debf43f20b6e498

f34a66abe0d68aa9e9250d5fea5c5a537be067859159164a917c667923d51d0c

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for phx-core4 (version 8.0.0).
If you installed it — respond
Remove phx-core4 from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If phx-core4 was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. phx-core4 on npm has been identified as a malicious package (version 8.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-01486

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks phx-core4-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database