Which versions of eip712-lite are malicious?

The following npm versions of eip712-lite 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 eip712-lite if I installed it?

eip712-lite 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 eip712-lite — how do I know if it already compromised me?

If eip712-lite 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.

Is eip712-lite part of a known attack campaign?

Yes — eip712-lite is associated with the GHSA-p5jf-vqp6-95h5, IN-MAL-2026-019054, IN-MAL-2026-019056, IN-MAL-2026-019578, IN-MAL-2026-019581 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 eip712-lite across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for eip712-lite (4 malicious versions).

Malicious package

eip712-litenpm

Advisory published Aug 28, 2026Updated Sep 4, 2026

eip712-lite is a confirmed malicious npm package (MAL-2026-15491) 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 eip712-lite (npm)

MAL-2026-15491

Immediate action

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

npm uninstall eip712-lite

What this malware does

index.js contains an IIFE that fires on require() and walks the installer's home and project directories collecting.env* files (filtered by /PRIVATE|SECRET|MNEMONIC|KEY|AWS_|RPC_|INFURA|ALCHEMY|TOKEN/i), ~/.aws/credentials, ~/.aws/config, ~/.npmrc, ~/.gitconfig, ~/.git-credentials, ~/.config/gh/hosts.yml, ~/.bash_history, ~/.zsh_history, ~/.ssh/id_, ~/.foundry/keystores, AWS SSO/CLI caches, and credential-shaped process.env entries. The collected data is gzip+base64 packed and PUT to api.github.com/repos/wutang344/env-diagnostics/contents/d/dp-<rand>.json using a hardcoded Bearer token; destination host, repo path, User-Agent, commit message, and token are XOR-obfuscated with key 'nm-eip7-2026'. After scheduling the upload, a scrub() routine rewrites index.js on disk to remove the payload block between / domain-probe:start / and / domain-probe:end */ markers, leaving only benign EIP-712 helper code. Execution is skipped when process.env.CI or GITHUB_ACTIONS is set and an idempotency marker at os.tmpdir()/.e712-probe.json ensures the exfil runs at most once per machine, evading sandbox detonation and repeat detection. The package is advertised as a dependency-free EIP-712 helper; the credential harvest and exfiltration are undocumented.

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

4 flagged

1.0.01.0.11.0.21.0.3

Indicators of compromise (SHA-256)

335f032dd17ae091e59182512948031f0e0873631ccd5942e5bcf179a0878070

0bb8d4640ca63919533ea826766c735fb8a8bdf8501bb33187ae30f905d82fc2

7b05f87dbda31d4b6bc1a71935abffb33a65fae68ea794df529f35109c47e45e

43414306b04eaf2edb6e79acdd6c5b4fcf0a72e67f83591e9af35d9fc6ad0413

e1f42938f9ea5bf0c6ce38218107564f3e5c99ca712aa10684a5a9c4a703b5da

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for eip712-lite (4 malicious versions).
If you installed it — respond
eip712-lite 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 eip712-lite 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. eip712-lite 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

GHSA-p5jf-vqp6-95h5IN-MAL-2026-019054IN-MAL-2026-019056IN-MAL-2026-019578IN-MAL-2026-019581

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks eip712-lite-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