# MAL-2026-16470: Malicious code in z-deno-truth-bwhlsz (npm)


- **Type:** Malicious package
- **Package:** `z-deno-truth-bwhlsz` (npm)
- **Published:** 23 Sep 2026
- **Also known as:** GHSA-f8xr-gjfq-xfcp

## What is MAL-2026-16470?

MAL-2026-16470 is a malicious package in z-deno-truth-bwhlsz, published on 23 Sep 2026. 

### Official description

The package's `exports` field maps the `./package.json` subpath to `setup.js`, so any consumer resolving `require('z-deno-truth-bwhlsz/package.json')` executes JavaScript instead of reading the manifest. `setup.js` writes a Deno/Hono handler to `/tmp/h.tsx` that reads `/readflag`, `/flagserver`, `/app/backdoor.tsx`, and `/entrypoint.sh` from the host filesystem and returns their contents in the HTTP response, matching on a `hitcon{...}` pattern. The exports subpath hijack turns routine package-metadata resolution into arbitrary code execution on the installer, and the dropped file is a shipped exfiltration handler intended to be picked up by a Deno server on the host. While the file-read targets are specific to a CTF environment, the delivery mechanism (subpath hijack + filesystem drop) executes on any host that resolves the package's `./package.json` subpath.

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-16470?

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-16470 is a malicious package: z-deno-truth-bwhlsz (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-16470/ (Markdown: https://insights.sbomify.com/MAL-2026-16470/index.md)
```

## Sources

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

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