new-ts-helpernpm
new-ts-helper is a confirmed malicious npm package (MAL-2026-6227) that executes malicious code on install (malicious version 9.0.2). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in new-ts-helper (npm)
What this malware does
index.js imports child_process and at lines 101 and 117 invokes execSync to run bash and zsh commands. Lines 9, 194, and 195 use Buffer.from(..., 'base64').toString() to decode base64-encoded payloads, a common pattern for hiding the actual shell commands from casual review. The combination of base64-decoded strings being fed into execSync calls inside the main module is the canonical shape of an obfuscated runtime payload executor: any caller that requires this package, or any lifecycle/CLI path that loads index.js, will execute attacker-controlled shell commands decoded from the embedded base64 blobs. There is no documented benign reason for a 'helper' package to base64-decode strings and shell them out. Package name (new-ts-helper) also has the shape of a low-effort lure rather than an established TypeScript utility.
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
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for new-ts-helper (version 9.0.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging new-ts-helper across your stack and pipelines.
If you installed it — respond
Remove new-ts-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.
Did it already run?
If new-ts-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.
How O3 protects you
O3 blocks new-ts-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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks new-ts-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.