Which versions of eth-wallet-helpers are malicious?

The following npm versions of eth-wallet-helpers are flagged malicious: 1.0.0, 1.0.1, 1.0.2, 1.0.3. Treat any of these as compromised.

How do I remediate eth-wallet-helpers if I installed it?

eth-wallet-helpers is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed eth-wallet-helpers — how do I know if it already compromised me?

If eth-wallet-helpers 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 eth-wallet-helpers part of a known attack campaign?

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

Malicious package

eth-wallet-helpersnpm

eth-wallet-helpers is a confirmed malicious npm package (MAL-2026-10572) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.0.1, 1.0.2…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in eth-wallet-helpers (npm)

MAL-2026-10572

Immediate action

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

npm uninstall eth-wallet-helpers

What this malware does

On require of index.js, a delayed IIFE reads test/fixtures/keypairs.dat, base64-decodes it into ~/.cache-db/.node-sync/syncd.js (mode 0o700), and spawns it detached under Node. The dropped payload (decoded content begins '// phantom syncd v3') recursively scans the user's home directory for files matching wallet/seed/mnemonic/private-key/keystore/API-key keywords across many extensions, RSA-encrypts the collected material with an embedded public key, and uploads it to Pinata IPFS using hardcoded PINATA_KEY/PINATA_SECRET credentials, with CIDs also fetched through gateway.pinata.cloud, ipfs.io, and cloudflare-ipfs.com. Persistence is installed per platform: a 12-hour crontab entry on Linux ('0 */12 * * * /usr/bin/node <syncd.js>'), a schtasks 'WinNodeSync' scheduled task on Windows, and a LaunchAgent plist com.apple.syncd (StartInterval 43200) on macOS, each re-executing the dropped syncd.js. The fixture-file cover name (test/fixtures/keypairs.dat) and a 37-second setTimeout delay are used to evade sandboxes and scanners. The package's advertised purpose is wallet-address helper functions; the credential-harvest and persistence behavior is not part of that surface.

Malicious versions

4 flagged

1.0.01.0.11.0.21.0.3

Indicators of compromise (SHA-256)

517d465272a3a1d252e83e178bb263a1ccf600b42fed6d5aa1d110b9141fc77a

fa7d1dbbd390a245c0b383dee6d7c081f67bbc49df1e6d8009f9db2e6085c70c

fadbab19dff6c6111f23b1031ee2db153fb009116b7cba9d5e8e9caff4e1fa30

8239ed468f3503f51a20c13144c6f22f665b894c63c9c9c381c88bb1d190b79b

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for eth-wallet-helpers (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging eth-wallet-helpers across your stack and pipelines.
If you installed it — respond
eth-wallet-helpers is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If eth-wallet-helpers 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 eth-wallet-helpers 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. eth-wallet-helpers on npm has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.0.2, 1.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010478IN-MAL-2026-010510IN-MAL-2026-010512IN-MAL-2026-010524

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks eth-wallet-helpers-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database