livekit-agentsnpm
livekit-agents is a confirmed malicious npm package (MAL-2026-6555) that opens a backdoor for remote access (malicious versions 0.1.0, 0.2.0, 0.2.1…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in livekit-agents (npm)
What this malware does
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.
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
Backdoor / remote accessFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for livekit-agents (10 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging livekit-agents across your stack and pipelines.
If you installed it — respond
livekit-agents establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If livekit-agents 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 livekit-agents 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 livekit-agents-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.