Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

Malicious code in tsliverhome (npm)

0
Critical
Published: 05/14/2026 (05/14/2026, 19:25:45 UTC)
Source: GCVE Database
Product: tsliverhome

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.

Affected software

npmghsa
tsliverhome
Affected versions
=1.0.0=1.1.3=1.1.4=1.1.5=1.1.2=1.1.1

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

AILast updated: 07/07/2026, 00:36:21 UTC

Technical Analysis

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'.

Potential 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.

Mitigation Recommendations

No official patch or fix is available for this malicious package. 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.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Gcve Source
db.gcve.eu
Osv Id
MAL-2026-3775
Osv Schema Version
1.7.4
Aliases
["GHSA-pchc-8c97-59c8"]
Ecosystems
["npm"]
Database Specific Severity
null
Cvss Version
null

Threat ID: 6a4c341227e9c797195f7c91

Added to database: 07/06/2026, 23:02:42 UTC

Last enriched: 07/07/2026, 00:36:21 UTC

Last updated: 07/18/2026, 17:27:21 UTC

Views: 11

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

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

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses