Which versions of jwscube are malicious?

The following npm versions of jwscube are flagged malicious: 1.1.9. Treat any of these as compromised.

How do I remediate jwscube if I installed it?

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

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

Yes — jwscube is associated with the GHSA-69rh-554m-m3w8, RLMA-2026-05133 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 jwscube across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for jwscube (version 1.1.9).

Malicious package

jwscubenpm

Advisory published May 12, 2026Updated Jul 9, 2026

jwscube is a confirmed malicious npm package (MAL-2026-3612) that executes malicious code on install (malicious version 1.1.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in jwscube (npm)

MAL-2026-3612

Immediate action

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

npm uninstall jwscube

What this malware does

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

1.1.9

Indicators of compromise (SHA-256)

325d4311f3dd1d82c8f9ee1ddc19a767eb69adf0a338625c8ce1e9d40062dec7

bcdb501556eb28931d6a50a6b85bbd41aae2e53d96117cfd25726a056a9eff85

Detection & response playbook

Malicious package

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

Campaign

GHSA-69rh-554m-m3w8RLMA-2026-05133

References

Credits

ReversingLabs · finder

Detect & block this

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