Which versions of string-tools-be6c are malicious?

The following npm versions of string-tools-be6c are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate string-tools-be6c if I installed it?

Remove string-tools-be6c 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 network activity or persistence. Use O3 Security's dependency scanner to confirm the package and its artifacts are fully purged across your stack.

Is string-tools-be6c part of a known attack campaign?

Yes — string-tools-be6c is associated with the IN-MAL-2026-006965, GHSA-93cp-5ff7-p9m5 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

Can O3 Security detect string-tools-be6c in my codebase?

Yes. O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, blocking string-tools-be6c and packages like it before any post-install script runs.

Malicious package

string-tools-be6cnpm

Malicious code in string-tools-be6c (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-6100

Immediate action

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

npm uninstall string-tools-be6c

What this malware does

Package ships a postinstall lifecycle hook (node run.js) that runs automatically on npm install. The executed script imports os, https, http, and child_process, reads host identifiers via os.hostname() and os.platform(), and issues outbound HTTP/HTTPS POST requests. This combination — install-time auto-execution + host-identity collection + outbound POSTs + child_process — is the canonical install-time host-beacon / dropper shape. The package name (string-tools-be6c) is a generic-name + random-hex-suffix pattern characteristic of throwaway supply-chain attack publications with no legitimate utility matching the observed runtime behavior.

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

Indicators of compromise (SHA-256)

c725b56cc7e80c178e8d0fca3eceb069e811b979427b6ec99deab6b6f6cab8f7

c3354cd2bf560462cd49d85f56db444163db078aba1c0b9b2e468cb0a123a29c

Frequently asked questions

No. string-tools-be6c on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-006965GHSA-93cp-5ff7-p9m5

References

Credits

Amazon Inspector · finder

Scan your dependencies

O3 Security blocks malicious packages like this at install time and in CI.

Supply-chain protection