Which versions of phx-core are malicious?

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

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

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

If phx-core was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is phx-core part of a known attack campaign?

Yes — phx-core is associated with the GHSA-jfqw-pq2x-x7rg, RLMA-2026-01482 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-core across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for phx-core (version 9.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging phx-core across your stack and pipelines.

Malicious package

phx-corenpm

Malicious code in phx-core (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-192572

Immediate action

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

npm uninstall phx-core

What this malware does

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

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

9.0.0

Indicators of compromise (SHA-256)

44cd2845eda5ed69922e3450a19b821ff762b61ea14e981648e9637faafcee3d

6b09229dc15cf8c3ce04a8a0a7e5cb43d43587ada9469f2a238c46a52927f94d

63cd1ecc7692e70c4d6562c00fdd5f873108d1419ed77312b9fc9d62997e3b87

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for phx-core (version 9.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging phx-core across your stack and pipelines.
If you installed it — respond
Remove phx-core 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-core was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks phx-core before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

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

Campaign

GHSA-jfqw-pq2x-x7rgRLMA-2026-01482

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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