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?

string-tools-be6c establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed string-tools-be6c — how do I know if it already compromised me?

If string-tools-be6c was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

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.

How do I find string-tools-be6c across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for string-tools-be6c (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging string-tools-be6c across your stack and pipelines.

Malicious package

string-tools-be6cnpm

string-tools-be6c is a confirmed malicious npm package (MAL-2026-6100) that opens a backdoor for remote access (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in string-tools-be6c (npm)

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

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for string-tools-be6c (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging string-tools-be6c across your stack and pipelines.
If you installed it — respond
string-tools-be6c establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If string-tools-be6c was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks string-tools-be6c before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

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

Detect & block this

O3 blocks string-tools-be6c-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database