Which versions of phx-core2 are malicious?

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

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

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

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

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

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

Malicious package

phx-core2npm

Advisory published Mar 18, 2026Updated Mar 23, 2026

phx-core2 is a confirmed malicious npm package (MAL-2026-1811) 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-core2 (npm)

MAL-2026-1811

Immediate action

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

npm uninstall phx-core2

What this malware does

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

Malicious versions

1 flagged

8.0.0

Indicators of compromise (SHA-256)

e09d53cab6cefa77e6d26527d5bd83add468067c52f02e08f9437d0319135f77

89f16048cf715ae2bb42dbbc5fc0019727991f8d5e94f05ec32361f543f453af

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for phx-core2 (version 8.0.0).
If you installed it — respond
Remove phx-core2 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-core2 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-core2 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-01484

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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