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

sorrawit-dev-helpernpm

sorrawit-dev-helper is a confirmed malicious npm package (MAL-2026-16344) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in sorrawit-dev-helper (npm)

MAL-2026-16344
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall sorrawit-dev-helper

What this malware does

package.json declares a postinstall lifecycle script that runs automatically on npm install. The script reads /tmp/flag.txt from the installer's machine and sends its URL-encoded contents as a query parameter to a hardcoded ngrok tunnel at https://ca37-49-237-83-218.ngrok-free.app/. The destination is an ephemeral tunnel host unrelated to any legitimate publisher, and the read+exfil fires without user interaction. The behavior matches install-time credential/file exfiltration with a concrete installer-side data source and a concrete attacker-controlled destination.

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

c64040dcfbbdb6ce434caf3cd5bd2baa518cc00970281a69f5309d57a4621233

Detection & response playbook

Credential / info stealer
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for sorrawit-dev-helper (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 sorrawit-dev-helper across your stack and pipelines.

  2. If you installed it — respond

    sorrawit-dev-helper 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.

  3. Did it already run?

    If sorrawit-dev-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 sorrawit-dev-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. sorrawit-dev-helper 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-020228

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks sorrawit-dev-helper-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

sorrawit-dev-helper (npm) malicious package — MAL-2026-16344 | O3 Security