Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

string-setup-helpernpm

string-setup-helper is a confirmed malicious npm package (MAL-2025-47206) that executes malicious code on install (malicious versions 1.0.0, 1.0.1, 1.0.2…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in string-setup-helper (npm)

MAL-2025-47206
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall string-setup-helper

What this malware does

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

28 flagged
1.0.01.0.11.0.21.0.31.0.41.0.51.0.61.0.71.0.81.0.91.0.101.0.111.0.131.0.141.0.151.0.161.0.171.0.181.0.191.0.201.0.211.0.221.0.231.0.241.0.251.0.261.0.271.0.28

Indicators of compromise (SHA-256)

0bc9eeb3a1bc272c3b55d695ba0aa54a481cfb3ac6c0611bbaadd96cf5cb1935
2a8d721203b80702fb65eee08af4e23b7ce71fd5f1a181bf258793ba73c72a8c
11546fb7b2a0eddbb12d6697c9b2c786f88b2ebd30e53f880d3e7d121609a5ca
6d1dd5bfe308499c8c0a5d9094b5d8bef59323e2232ce580004d940ebd5169c4
6e416c28e3449e2b115d8585865f412aebfae5a2f38bb7a3a1b2541bc5544775

Detection & response playbook

Malicious package
  1. Find it

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

  2. If you installed it — respond

    Remove string-setup-helper 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.

  3. Did it already run?

    If string-setup-helper 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.

  4. How O3 protects you

    O3 blocks string-setup-helper 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-setup-helper on npm has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.5, 1.0.6, 1.0.7, and 20 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-wxx7-r3f9-m7v2RLMA-2025-05165RLUA-2026-01595

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks string-setup-helper-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.

Explore

string-setup-helper (npm) malicious package — MAL-2025-47206 | O3 Security