MAL-2026-4815 Malicious code in @slipless/sdk (npm)
Malicious package
Published
MAL-2026-4815 is a malicious package: @slipless/sdk (npm). Every version was published to cause harm.
Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.
Reference: https://insights.sbomify.com/MAL-2026-4815/ (Markdown: https://insights.sbomify.com/MAL-2026-4815/index.md)
- Package
- @slipless/sdk
- Registry
- npm
What is MAL-2026-4815?
MAL-2026-4815 is a malicious package in @slipless/sdk, published on 26 May 2026.
Official description
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.What should I do about MAL-2026-4815?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.