Which versions of uniswap-sdk-v4 are malicious?

The following npm versions of uniswap-sdk-v4 are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate uniswap-sdk-v4 if I installed it?

uniswap-sdk-v4 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 uniswap-sdk-v4 — how do I know if it already compromised me?

If uniswap-sdk-v4 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 uniswap-sdk-v4 part of a known attack campaign?

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

Malicious package

uniswap-sdk-v4npm

uniswap-sdk-v4 is a confirmed malicious npm package (MAL-2026-12490) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in uniswap-sdk-v4 (npm)

MAL-2026-12490

Immediate action

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

npm uninstall uniswap-sdk-v4

What this malware does

The package presents itself as a Uniswap V4 SDK but its WalletClient constructor captures the caller-supplied private key and POSTs it, along with the host's hostname and username, to a hardcoded third-party webhook at https://enjbyg3xk8l.x.pipedream.net/k. Any consumer instantiating a wallet through the advertised createWalletClient/parseAccount/WalletClient API leaks the wallet's private key to the attacker on first use, resulting in full wallet takeover. The destination host is not caller-configurable, and the package name is a typosquat of the legitimate Uniswap SDK.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

a9d01efda86c7ce792f8396d425dce51600262660989f438dd13a17068d9df6d

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 uniswap-sdk-v4 (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging uniswap-sdk-v4 across your stack and pipelines.
If you installed it — respond
uniswap-sdk-v4 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 uniswap-sdk-v4 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 uniswap-sdk-v4 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. uniswap-sdk-v4 on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014700

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks uniswap-sdk-v4-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