Which versions of jqxcore are malicious?

The following npm versions of jqxcore are flagged malicious: 99.0.0. Treat any of these as compromised.

How do I remediate jqxcore if I installed it?

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

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

Yes — jqxcore is associated with the RLMA-2025-05820 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 jqxcore across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for jqxcore (version 99.0.0).

Malicious package

jqxcorenpm

Advisory published Dec 1, 2025Updated Dec 2, 2025

jqxcore is a confirmed malicious npm package (MAL-2025-191576) that executes malicious code on install (malicious version 99.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in jqxcore (npm)

MAL-2025-191576

Immediate action

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

npm uninstall jqxcore

What this malware does

The package jqxcore was found to contain malicious code.

Malicious versions

1 flagged

99.0.0

Indicators of compromise (SHA-256)

fca94f2c7c0faa19ebe788a5ddfc2412f581613f1d87343c5752ac9fda628254

71dc7d7d1018099bd9860ca26eea2e4dab1963220ba836768cda991ba135b073

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-05820

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks jqxcore-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