Which versions of jsxswap are malicious?

The following npm versions of jsxswap are flagged malicious: 7.2.7. Treat any of these as compromised.

How do I remediate jsxswap if I installed it?

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

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

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

Search your lockfiles and build artifacts for jsxswap (version 7.2.7).

Malicious package

jsxswapnpm

Advisory published Dec 23, 2025Updated Jan 2, 2026

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

Malicious code in jsxswap (npm)

MAL-2025-192816

Immediate action

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

npm uninstall jsxswap

What this malware does

The package jsxswap was found to contain malicious code.

Malicious versions

1 flagged

7.2.7

Indicators of compromise (SHA-256)

e389917685571ef12e717587d880e287c89287da5f40e0ca4e8d2862d85f5313

9e585d962028222230a55c3961d69f50420d32cbc534e13042f3763d6f77110d

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-06382

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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