Which versions of @sameepsi/sor are malicious?

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

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

@sameepsi/sor 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/sor — how do I know if it already compromised me?

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

Yes — @sameepsi/sor is associated with the GHSA-jwrx-rx3q-v25q 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/sor across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @sameepsi/sor (2 malicious versions).

Malicious package

@sameepsi/sornpm

Advisory published Nov 24, 2025Updated Dec 1, 2025

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

Malicious code in @sameepsi/sor (npm)

MAL-2025-191309

Immediate action

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

npm uninstall @sameepsi/sor

What this malware does

The package @sameepsi/sor 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

2 flagged

1.0.32.0.2

Indicators of compromise (SHA-256)

bf2de6989bf415499d8a038f6c718e5755e99426a717994d1dce074ced64381b

d04547ce27d4c15e2f969770ddc25732ef8f72d46eb21e8dc06f11fc1dc8eea9

3adb16c7fa87468a84d44a406817901611ecd6abd880920f77cd1ac25e7ff0b7

c938c06786ba13f7feed4114c84d12806a6c7ce595360985be178a8ae4844257

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for @sameepsi/sor (2 malicious versions).
If you installed it — respond
@sameepsi/sor 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/sor 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/sor on npm has been identified as a malicious package (versions 1.0.3, 2.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-jwrx-rx3q-v25q

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @sameepsi/sor-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