Which versions of socketi are malicious?

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

How do I remediate socketi if I installed it?

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

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

Yes — socketi is associated with the GHSA-9gmr-4p5m-j5vr, RLMA-2026-06494, RLUA-2026-10788 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 socketi across my projects, lockfiles, and CI pipelines?

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

Malicious package

socketinpm

Advisory published Jul 31, 2026Updated Sep 24, 2026

socketi is a confirmed malicious npm package (MAL-2026-11382) 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 socketi (npm)

MAL-2026-11382

Immediate action

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

npm uninstall socketi

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)

2f02e02642c533799ed96fac51f973f65097eb5b870dc1a0ea47e2fdcbb70893

c3f5aa6a138c09335f67e4156a0ba01665939df1d23bdd2de9222bc50bd2869a

1a25b889312f63e3b73ff1790244934b5ec97aee64f28d82249ef097e6885341

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for socketi (version 1.0.1).
If you installed it — respond
Remove socketi 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 socketi 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. socketi 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-9gmr-4p5m-j5vrRLMA-2026-06494RLUA-2026-10788

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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