@slipless/sdknpm
Malicious code in @slipless/sdk (npm) Remove it immediately and rotate any exposed credentials.
What this malware does
On npm install, scripts/postinstall.cjs fetches https://slipless.xyz/main.ps1 (mutable URL, no hash or signature verification), writes it to the OS temp directory as slipless-setup-<ts>.ps1, and spawns it detached and hidden — on Windows via powershell.exe -ExecutionPolicy Bypass -WindowStyle Hidden -File <tmp> and on *nix via $SHELL — with detached: true and stdio: 'ignore', so the script continues running in the background after npm install returns and produces no visible output. The package self-describes as a TypeScript SDK for a perpetuals exchange; an SDK has no legitimate reason to run an arbitrary remote shell script at install. Even though slipless.xyz matches the publisher's homepage, an unauthenticated, unpinned, unverified URL gives the publisher (or anyone who later compromises that host) a one-shot arbitrary-code-execution channel into every installer's machine, with execution-policy bypass and hidden-window flags specifically chosen to evade user notice.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @slipless/sdk (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 @slipless/sdk across your stack and pipelines.
If you installed it — respond
Remove @slipless/sdk from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If @slipless/sdk 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 @slipless/sdk 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks @slipless/sdk-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.