Which versions of @aerodrome-finance/slipstream are malicious?

The following npm versions of @aerodrome-finance/slipstream are flagged malicious: 1.0.0, 1.1.0, 1.1.1. Treat any of these as compromised.

How do I remediate @aerodrome-finance/slipstream if I installed it?

@aerodrome-finance/slipstream 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 @aerodrome-finance/slipstream — how do I know if it already compromised me?

If @aerodrome-finance/slipstream 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 @aerodrome-finance/slipstream part of a known attack campaign?

Yes — @aerodrome-finance/slipstream is associated with the IN-MAL-2026-017369, IN-MAL-2026-017352, IN-MAL-2026-017368 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 @aerodrome-finance/slipstream 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 @aerodrome-finance/slipstream (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @aerodrome-finance/slipstream across your stack and pipelines.

Malicious package

@aerodrome-finance/slipstreamnpm

@aerodrome-finance/slipstream is a confirmed malicious npm package (MAL-2026-13735) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.1.0, 1.1.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @aerodrome-finance/slipstream (npm)

MAL-2026-13735

Immediate action

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

npm uninstall @aerodrome-finance/slipstream

What this malware does

Package published as @aerodrome-finance/slipstream advertises 'Aerodrome Slipstream AMM contracts and ABIs' but ships only index.js, which is executed via preinstall and postinstall lifecycle hooks. On install, index.js enumerates process.env filtering keys matching a credential regex (KEY|TOKEN|SECRET|PASS|PRIVATE|MNEMONIC|AWS|GITHUB|NPM|WALLET|SEED|...), reads installer-side secret files including ~/.aws/credentials, ~/.ssh/id_rsa and id_ed25519, ~/.npmrc, ~/.netrc, ~/.docker, ~/.foundry/keystores, Solana/Sui key material, and.env files, serializes the collected data, and hands it off to a detached Node subprocess (spawn(process.execPath, ['-e', src], {detached:true, stdio:'ignore'}); ch.unref()) that sleeps 60-240 seconds before POSTing the JSON payload to https://webhook.site/326b0891-2093-4800-a4c1-686ce3e07b09. The code also bails out when hostname/user match sandbox indicators (scan-, detonation, sandbox, ubuntu-fc-uvm, honey, canarytokens, npmmirror), evading install-time sandbox observation. The package name impersonates the Aerodrome Finance DeFi project and the harvest list targets crypto/DeFi developers (wallet keystores, RPC provider tokens, Foundry/Solana/Sui keys).

Malicious versions

3 flagged

1.0.01.1.01.1.1

Indicators of compromise (SHA-256)

27c46eca00f87ce74b48f8ea455991a215d32c291cd503c882be3d8d1269045a

d9834357b7108ed122b3c272b3f913e0d2e931ab3629e94227b61f787fbe2525

9e159c53351fbfabd3b79afa787fb222f18e0ee7745503064e351cb693b4b2ff

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

Campaign

IN-MAL-2026-017369IN-MAL-2026-017352IN-MAL-2026-017368

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @aerodrome-finance/slipstream-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