Which versions of soccketio are malicious?

The following npm versions of soccketio are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate soccketio if I installed it?

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

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

Yes — soccketio is associated with the GHSA-6j64-8q3f-7w69, RLMA-2026-06493, RLUA-2026-10787 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 soccketio across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for soccketio (version 1.0.1).

Malicious package

soccketionpm

Advisory published Jul 31, 2026Updated Sep 24, 2026

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

Malicious code in soccketio (npm)

MAL-2026-11381

Immediate action

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

npm uninstall soccketio

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.0.1

Indicators of compromise (SHA-256)

9fc9cac2969243ba864ef1645d5d99ed62e8e4906bc58cd32cee3fad42c9c528

1911105313d5d43c18130dd705b9a58c5485b92c6ef0df76b019597a67ffcd98

84f9533ccb954c55a4ed837b6ede67efa2033e82a7371de3b6906ea8fd2e6d9e

Detection & response playbook

Malicious package

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

Campaign

GHSA-6j64-8q3f-7w69RLMA-2026-06493RLUA-2026-10787

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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