Which versions of js-to-solve are malicious?

The following npm versions of js-to-solve are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate js-to-solve if I installed it?

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

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

Yes — js-to-solve is associated with the RLMA-2026-01364 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 js-to-solve across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for js-to-solve (version 1.0.0).

Malicious package

js-to-solvenpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

js-to-solve is a confirmed malicious npm package (MAL-2026-1756) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in js-to-solve (npm)

MAL-2026-1756

Immediate action

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

npm uninstall js-to-solve

What this malware does

The package js-to-solve was found to contain malicious code.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

640beaed273f6d0aa9b7837cbc375bdd7008137877bfebc97b85e0a33be6e3d5

5bfe1e90f37563cf60de25fd9a1b84330e34f96b0636d0fd5a4a323c7eb52890

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01364

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks js-to-solve-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