MalwarePublished 14 May 2026Updated 6 Jul 2026

tsliverhome (npm) · Malicious Code

Affects tsliverhomeSource GCVE Database

Malicious package : remove tsliverhome and rotate any secrets on hosts that installed it.

Data as of 7 Jul 2026, 12:28 UTC

Classification

Malicious package

Published to npm · OSV MAL-2026-3775

What to do

Remove tsliverhome from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.

Affected software

Product	Affected	Fixed in
npmtsliverhome	Affected 1.0.0 – 1.1.5 6 affected builds	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (0855b4d02a0d276e8a6cf97b7c62d457b8ef4d851e243d758c2308d451e0876e) Package name 'tsliverhome' impersonates the widely-used 'tslib' package (~300M weekly downloads). The shipped README.md is a verbatim copy of Microsoft/tslib's README (titled '# tsliv', describing the TypeScript --importHelpers runtime library), designed to reassure a developer who mistyped the name. The actual code in index.js has no relation to tslib: the exported getPlugin() function issues an HTTP GET to https://verceljs-kappa.vercel.app/icons/23, JSON.parses the response body, and passes it directly to eval(). The destination is a generic Vercel preview-style host not tied to any declared publisher, is not version-pinned, and the fetched bytes are not hash- or signature-verified. Any consumer who imports this package and calls getPlugin() will execute arbitrary JavaScript under the control of whoever operates verceljs-kappa.vercel.app. Supporting signals: package.json ships placeholder metadata (empty description, empty author, no repository, no homepage), consistent with throwaway-publisher typosquat packages. The combination of (a) name-confusion with a top-tier target, (b) README impersonation of that target, and (c) a remote-fetch-and-eval payload in the exported API constitutes a deliberate supply-chain attack against developers who mistype 'tslib'. ## Source: ghsa-malware (5f777a818727586bf6ad1ea484dc9ca687dcbf4108a4292564c88ef1fb0bc159) 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.

Impact

Any system that installs and runs the 'tsliverhome' package and calls its getPlugin() function is at risk of arbitrary code execution controlled by an attacker. This can lead to full system compromise, including unauthorized access to secrets and keys stored on the machine. The compromise is severe enough that all credentials on the affected system should be considered exposed and rotated from a separate, trusted environment. Removal of the package alone does not guarantee eradication of all malicious artifacts.

Defensive guidance

The recommended mitigation is to immediately remove the 'tsliverhome' package from any affected systems. Additionally, rotate all secrets and keys that may have been exposed due to the compromise, using a different, secure machine. Developers should verify package names carefully before installation to avoid typosquatting attacks. Since this is a malicious package rather than a vulnerability in legitimate software, prevention through careful dependency management and use of trusted package sources is critical.

Summary

The 'tsliverhome' package on npm impersonates the popular 'tslib' package by copying its README and using a similar name to trick developers. Instead of providing legitimate functionality, its exported getPlugin() function performs an HTTP GET request to a remote Vercel-hosted URL, parses the JSON response, and executes it via eval() without any integrity verification. This behavior allows attackers controlling the remote server to execute arbitrary JavaScript code on any system that imports and invokes this function. The package metadata lacks credible information, consistent with a throwaway typosquatting attack. This constitutes a deliberate supply-chain attack targeting developers who mistype 'tslib'.

References

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 7 Jul 2026, 00:36 UTC

Technical details

References

Community reviews