Which versions of phx-core3 are malicious?

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

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

Remove phx-core3 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-core3 — how do I know if it already compromised me?

If phx-core3 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-core3 part of a known attack campaign?

Yes — phx-core3 is associated with the RLMA-2026-01485 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-core3 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for phx-core3 (2 malicious versions).

Malicious package

phx-core3npm

Advisory published Mar 18, 2026Updated Mar 23, 2026

phx-core3 is a confirmed malicious npm package (MAL-2026-1812) that executes malicious code on install (malicious versions 8.0.0, 8.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in phx-core3 (npm)

MAL-2026-1812

Immediate action

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

npm uninstall phx-core3

What this malware does

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

Malicious versions

2 flagged

8.0.08.0.1

Indicators of compromise (SHA-256)

3f2c4fe3f7604684972e5278bc5fc39fc3d64a4347bc4b0e3d3b39338d51583a

c182980686938a51acd427be3197fc50c4af1d05945b77563405f764c7b910c6

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for phx-core3 (2 malicious versions).
If you installed it — respond
Remove phx-core3 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-core3 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-core3 on npm has been identified as a malicious package (versions 8.0.0, 8.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-01485

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks phx-core3-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