Which versions of uniswap-smart-order-router are malicious?

The following npm versions of uniswap-smart-order-router are flagged malicious: 3.16.26. Treat any of these as compromised.

How do I remediate uniswap-smart-order-router if I installed it?

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

If uniswap-smart-order-router 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-smart-order-router part of a known attack campaign?

Yes — uniswap-smart-order-router is associated with the GHSA-4jp7-ch66-mvmv 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-smart-order-router 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-smart-order-router (version 3.16.26). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging uniswap-smart-order-router across your stack and pipelines.

Malicious package

uniswap-smart-order-routernpm

Malicious code in uniswap-smart-order-router (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191442

Immediate action

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

npm uninstall uniswap-smart-order-router

What this malware does

The package uniswap-smart-order-router was found to contain malicious code.

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.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

1 flagged

3.16.26

Indicators of compromise (SHA-256)

6cbc7778302ead2cbd4c4df0a498581cacaedafb7ba48ed309a88d3acd7d0faa

8e676e2f4d6d8d478177d9c837911e457a604a2e956766919be73504bbf450c5

4dbda3147fde915a97ddd97f51f5ebc1757fa14bca7cad95f333862ad125c3c1

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

Campaign

GHSA-4jp7-ch66-mvmv

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks uniswap-smart-order-router-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