Which versions of @sameepsi/sor2 are malicious?

The following npm versions of @sameepsi/sor2 are flagged malicious: 2.0.2. Treat any of these as compromised.

How do I remediate @sameepsi/sor2 if I installed it?

@sameepsi/sor2 is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed @sameepsi/sor2 — how do I know if it already compromised me?

If @sameepsi/sor2 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 @sameepsi/sor2 part of a known attack campaign?

Yes — @sameepsi/sor2 is associated with the GHSA-rq97-rqcj-h44v 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 @sameepsi/sor2 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @sameepsi/sor2 (version 2.0.2).

Malicious package

@sameepsi/sor2npm

Advisory published Nov 24, 2025Updated Dec 1, 2025

@sameepsi/sor2 is a confirmed malicious npm package (MAL-2025-191310) that steals credentials and exfiltrates sensitive data (malicious version 2.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @sameepsi/sor2 (npm)

MAL-2025-191310

Immediate action

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

npm uninstall @sameepsi/sor2

What this malware does

The package @sameepsi/sor2 was found to contain malicious code.

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.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

1 flagged

2.0.2

Indicators of compromise (SHA-256)

4cee03e5382aa4e7eb51461b1c22a6bd60f0673165eadee2acfff6f1b3c56201

2d34ad4c15350b1f697d541469fe980138a8d60a6abf768fcc4c6365a9d186d6

2c5470b040485c9e91f7985d59bd1b1754daed9d80ab9545426cfcf57d627928

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for @sameepsi/sor2 (version 2.0.2).
If you installed it — respond
@sameepsi/sor2 is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @sameepsi/sor2 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. @sameepsi/sor2 on npm has been identified as a malicious package (version 2.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-rq97-rqcj-h44v

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @sameepsi/sor2-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database