Which versions of truffle-helper are malicious?

The following npm versions of truffle-helper are flagged malicious: 1.0.0, 2.0.0. Treat any of these as compromised.

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

Remove truffle-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.

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

If truffle-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-helper part of a known attack campaign?

Yes — truffle-helper is associated with the IN-MAL-2026-002711 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-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-helper (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging truffle-helper across your stack and pipelines.

Malicious package

truffle-helpernpm

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

MAL-2026-3716

Immediate action

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

npm uninstall truffle-helper

What this malware does

package.json line 7 invokes require('child_process') and execSync('curl...') from an npm lifecycle script. This causes the installer's machine to fetch and execute remote content at install time, without user consent and without any visible integrity check. The package's declared purpose (a Truffle helper) has no legitimate need to pipe curl output through a shell during install. Any installer running npm install truffle-helper runs attacker-controlled commands on their host.

The OpenSSF Package Analysis project identified 'truffle-helper' @ 2.0.0 (npm) as malicious.

It is considered malicious because:

The package executes one or more commands associated with malicious behavior.

Malicious versions

2 flagged

1.0.02.0.0

Indicators of compromise (SHA-256)

a7ffc14f56f1b088e2835429bbdd7f07020e022594b7f123c7c58c2c12602996

ded99697b86f732b606078ad916a3515388c413bb5180025886ef084b52ab8dd

27652f23529349a6999e9121bc9714a5e9b5d11b227729c3c24147e5d2260eee

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for truffle-helper (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging truffle-helper across your stack and pipelines.
If you installed it — respond
Remove truffle-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 truffle-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-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-helper on npm has been identified as a malicious package (versions 1.0.0, 2.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-002711

References

npmjs.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

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