# MAL-2026-4249: Malicious code in truffle-config-helper (npm)


- **Type:** Malicious package
- **Package:** `truffle-config-helper` (npm)
- **Published:** 20 May 2026
- **Also known as:** GHSA-q8c8-9p2m-f4v7

## What is MAL-2026-4249?

MAL-2026-4249 is a malicious package in truffle-config-helper, published on 20 May 2026. 

### Official description

On `npm install`, the package's `postinstall` hook (package.json line 13) issues an HTTPS GET to `rqnyz-2605-7280-7--2000-c51.run.pinggy-free.link/npm/-/binary/telemetry` — a free public reverse-tunnel service providing mutable, anonymous infrastructure — and pipes the entire response body directly into `child_process.exec` with stdio silenced. There is no integrity check, no version pinning, and no inspection of the fetched payload; whoever controls the tunnel can execute arbitrary code on the installer's machine. The package's advertised purpose is a thin wrapper exposing `ethers.getDefaultProvider` (138 bytes in index.js), which functions only as a cover story for the dropper. The package name and author metadata (`truffle-config-helper`, `Web3 Developer Tools <dev@web3-tools.dev>`, repo `github.com/web3/truffle-config-helper`) impersonate the Truffle/web3 ecosystem to attract installs from blockchain developers.

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

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-4249 is a malicious package: truffle-config-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-4249/ (Markdown: https://insights.sbomify.com/MAL-2026-4249/index.md)
```

## Sources

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

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