Malicious code in livekit-agents (npm)
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (5abf921f58c69745fee91e812853b493a282f3d42f55db38516ba54b827ea35b) The unscoped npm package `livekit-agents` advertises itself in README as the official LiveKit Agents SDK and links to livekit.io documentation, but the shipped library at `dist/index.js` implements only a trivial stub `greet(name)` returning a hello string — none of the real SDK surface. The bundled CLI at `dist/cli.js` (the package `bin`) calls `sendCliMetric()` at the top of every invocation, unconditionally POSTing `{type:'cli_run', nodeVersion, platform, arch, timestamp}` to `https://livekit-agents.xyz/api/metrics`. The destination `livekit-agents.xyz` is a lookalike domain — LiveKit's real domain is livekit.io — and the beacon is undocumented with no opt-out. `package.json` also declares `"postinstall": "node scripts/postinstall.js"` while `files` ships only `dist`, so the referenced install hook is absent from this tarball (a no-op today, but pre-wired for a future version). Combined signals — name impersonation of the real scoped package, stub implementation, covert install-base telemetry to an author-controlled lookalike domain, and a pre-wired but currently empty postinstall slot — match the namespace-abuse / typosquat pattern used to enumerate victims before delivering a later payload. ## Source: ghsa-malware (b3267568f730dc62727262d724d6b6831f262d1a6892febe6d2c1ac350b3951c) 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 unscoped npm package 'livekit-agents' falsely advertises itself as the official LiveKit Agents SDK but only implements a trivial stub function. It covertly sends telemetry data including environment details to a malicious lookalike domain 'livekit-agents.xyz', which is not affiliated with the legitimate 'livekit.io' domain. The package's 'postinstall' script is declared but currently absent, suggesting preparation for future malicious actions. This pattern of namespace abuse and telemetry collection is consistent with typosquatting attacks aimed at enumerating victims before deploying further payloads. The package versions 0.3.0, 0.3.1, 0.3.2, and 0.3.4 are affected. Any system with this package installed should be considered fully compromised.
Potential Impact
Systems with this package installed or running are considered fully compromised. The package collects and sends environment telemetry to an attacker-controlled domain without user consent or documentation. This may lead to unauthorized data exposure. The presence of a pre-wired postinstall hook indicates potential for future malicious payload delivery. Secrets and keys stored on compromised systems should be rotated immediately from a secure environment. Removing the package alone may not eliminate all malicious software introduced.
Mitigation Recommendations
Remove the 'livekit-agents' package immediately from all affected systems. Rotate all secrets and keys stored on compromised machines from a separate, secure environment. Monitor for any signs of persistent compromise, as full control may have been granted to attackers. There is no official patch or fix since this is a malicious package impersonation; avoidance and removal are the primary mitigations.
Malicious code in livekit-agents (npm)
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (5abf921f58c69745fee91e812853b493a282f3d42f55db38516ba54b827ea35b) The unscoped npm package `livekit-agents` advertises itself in README as the official LiveKit Agents SDK and links to livekit.io documentation, but the shipped library at `dist/index.js` implements only a trivial stub `greet(name)` returning a hello string — none of the real SDK surface. The bundled CLI at `dist/cli.js` (the package `bin`) calls `sendCliMetric()` at the top of every invocation, unconditionally POSTing `{type:'cli_run', nodeVersion, platform, arch, timestamp}` to `https://livekit-agents.xyz/api/metrics`. The destination `livekit-agents.xyz` is a lookalike domain — LiveKit's real domain is livekit.io — and the beacon is undocumented with no opt-out. `package.json` also declares `"postinstall": "node scripts/postinstall.js"` while `files` ships only `dist`, so the referenced install hook is absent from this tarball (a no-op today, but pre-wired for a future version). Combined signals — name impersonation of the real scoped package, stub implementation, covert install-base telemetry to an author-controlled lookalike domain, and a pre-wired but currently empty postinstall slot — match the namespace-abuse / typosquat pattern used to enumerate victims before delivering a later payload. ## Source: ghsa-malware (b3267568f730dc62727262d724d6b6831f262d1a6892febe6d2c1ac350b3951c) 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 unscoped npm package 'livekit-agents' falsely advertises itself as the official LiveKit Agents SDK but only implements a trivial stub function. It covertly sends telemetry data including environment details to a malicious lookalike domain 'livekit-agents.xyz', which is not affiliated with the legitimate 'livekit.io' domain. The package's 'postinstall' script is declared but currently absent, suggesting preparation for future malicious actions. This pattern of namespace abuse and telemetry collection is consistent with typosquatting attacks aimed at enumerating victims before deploying further payloads. The package versions 0.3.0, 0.3.1, 0.3.2, and 0.3.4 are affected. Any system with this package installed should be considered fully compromised.
Potential Impact
Systems with this package installed or running are considered fully compromised. The package collects and sends environment telemetry to an attacker-controlled domain without user consent or documentation. This may lead to unauthorized data exposure. The presence of a pre-wired postinstall hook indicates potential for future malicious payload delivery. Secrets and keys stored on compromised systems should be rotated immediately from a secure environment. Removing the package alone may not eliminate all malicious software introduced.
Mitigation Recommendations
Remove the 'livekit-agents' package immediately from all affected systems. Rotate all secrets and keys stored on compromised machines from a separate, secure environment. Monitor for any signs of persistent compromise, as full control may have been granted to attackers. There is no official patch or fix since this is a malicious package impersonation; avoidance and removal are the primary mitigations.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-6555
- Osv Schema Version
- 1.7.4
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a42ed7827e9c797199395c6
Added to database: 06/29/2026, 22:11:04 UTC
Last enriched: 07/09/2026, 10:48:12 UTC
Last updated: 07/26/2026, 05:58:16 UTC
Views: 35
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.