# MAL-2026-6227: Malicious code in new-ts-helper (npm)


- **Type:** Malicious package
- **Package:** `new-ts-helper` (npm)
- **Published:** 19 Jun 2026
- **Also known as:** GHSA-g793-594c-6gxf

## What is MAL-2026-6227?

MAL-2026-6227 is a malicious package in new-ts-helper, published on 19 Jun 2026. 

### Official description

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.

## What should I do about MAL-2026-6227?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-6227 is a malicious package: new-ts-helper (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-6227/ (Markdown: https://insights.sbomify.com/MAL-2026-6227/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-6227

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-6227/
Summaries are generated and may contain mistakes; the official description above is the record.