Which versions of truffle-config-helper are malicious?

The following npm versions of truffle-config-helper are flagged malicious: 1.7.0. Treat any of these as compromised.

How do I remediate truffle-config-helper if I installed it?

truffle-config-helper is a typosquat — you almost certainly intended a legitimately-named package. Remove truffle-config-helper, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed truffle-config-helper — how do I know if it already compromised me?

If truffle-config-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.

Is truffle-config-helper part of a known attack campaign?

Yes — truffle-config-helper is associated with the GHSA-q8c8-9p2m-f4v7, IN-MAL-2026-003337 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find truffle-config-helper across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for truffle-config-helper (version 1.7.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging truffle-config-helper across your stack and pipelines.

Malicious package

truffle-config-helpernpm

Malicious code in truffle-config-helper (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-4249

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall truffle-config-helper

What this malware does

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 <[email protected]>, 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.

Malicious versions

1 flagged

1.7.0

Indicators of compromise (SHA-256)

115a1b8afe0978034a9565602f9953e5d0c0aef608a6e13ec74b3f812768da57

2204d3386cd8473771610640812df94a0c65c5482027bd7a59282398d38e73db

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for truffle-config-helper (version 1.7.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging truffle-config-helper across your stack and pipelines.
If you installed it — respond
truffle-config-helper is a typosquat — you almost certainly intended a legitimately-named package. Remove truffle-config-helper, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If truffle-config-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 truffle-config-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. truffle-config-helper on npm has been identified as a malicious package (version 1.7.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-q8c8-9p2m-f4v7IN-MAL-2026-003337

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks truffle-config-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.

Malware detection Runtime egress monitoring