NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

truffle-jsnpm

Advisory published Updated

truffle-js is a confirmed malicious npm package (MAL-2026-3717) that typosquats a legitimate package to trick installs (malicious versions 1.0.0, 2.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in truffle-js (npm)

MAL-2026-3717
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall truffle-js

What this malware does

The package.json lifecycle script invokes require('child_process').execSync with a curl command at install time. Running curl through child_process during an npm install lifecycle hook causes any installer to execute remote content fetched over the network, without consent, as soon as npm install runs. The package name also resembles the widely-used 'truffle' Ethereum development toolkit, consistent with a typosquat lure. There is no legitimate reason for a small utility package to shell out to curl from its package.json install hook.

The OpenSSF Package Analysis project identified 'truffle-js' @ 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)

c190460255cf713f1797bacece635079c6d3db6a45a58199af29ab1acc9faa2f
52bd5b41de871fbbc8c5895f63dfec08ba2ff6ecb9ea03fa6fdb5d9245c74616

Detection & response playbook

Typosquat
  1. Find it

    Search your lockfiles and build artifacts for truffle-js (2 malicious versions).

  2. If you installed it — respond

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

  3. Did it already run?

    If truffle-js was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. truffle-js 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-002697

References

Credits

  • Amazon Inspector · finder
  • OpenSSF: Package Analysis · finder

Detect & block this

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

Explore

truffle-js (npm) malicious package — MAL-2026-3717 | O3 Security