Which versions of jsswapper are malicious?

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

How do I remediate jsswapper if I installed it?

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

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

Yes — jsswapper is associated with the RLMA-2025-06380, RLUA-2026-01381 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 jsswapper 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 jsswapper (version 7.2.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging jsswapper across your stack and pipelines.

Malicious package

jsswappernpm

Malicious code in jsswapper (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-192814

Immediate action

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

npm uninstall jsswapper

What this malware does

The package jsswapper was found to contain malicious code.

Malicious versions

1 flagged

7.2.7

Indicators of compromise (SHA-256)

e04a3a6b43822bf43ab8230c5ff270747c4c790631a969111bbb63cff09b30da

d7808f95622190dd5e4eadbaa97bd926083dc09c84afae6f6ced7c4c978763d6

fe6a3b289dd802663d86b9c34fd541e82ef7fe22fb859e666534c6969aefc1d3

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 jsswapper (version 7.2.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging jsswapper across your stack and pipelines.
If you installed it — respond
Remove jsswapper 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 jsswapper 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 jsswapper 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. jsswapper 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-06380RLUA-2026-01381

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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