Which versions of simple-string-utils3 are malicious?

Every published version of simple-string-utils3 on npm is considered malicious. Remove the package entirely.

How do I remediate simple-string-utils3 if I installed it?

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

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

Yes — simple-string-utils3 is associated with the GHSA-25cq-qhpp-pxcx 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 simple-string-utils3 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for simple-string-utils3 (all published versions).

Malicious package

simple-string-utils3npm

Advisory published Jan 12, 2026Updated Jan 15, 2026

simple-string-utils3 is a confirmed malicious npm package (MAL-2026-233) that executes malicious code on install. Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in simple-string-utils3 (npm)

MAL-2026-233

Immediate action

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

npm uninstall simple-string-utils3

What this malware does

The package simple-string-utils3 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.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

9bcda0e4d556b422287b7e58b0e9fdd4141e12767416e0fce014700965ba2d8d

13d9f9db863d718f528caa234dfa722b2631eb76195f504f47670898aeb0634a

Detection & response playbook

Malicious package

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

Campaign

GHSA-25cq-qhpp-pxcx

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks simple-string-utils3-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