Which versions of livekit-agents are malicious?

The following npm versions of livekit-agents are flagged malicious: 0.3.0, 0.3.1, 0.3.2. Treat any of these as compromised.

How do I remediate livekit-agents if I installed it?

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.

I already installed livekit-agents — how do I know if it already compromised me?

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.

Is livekit-agents part of a known attack campaign?

Yes — livekit-agents is associated with the IN-MAL-2026-007699, IN-MAL-2026-007698, IN-MAL-2026-007700 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find livekit-agents across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for livekit-agents (3 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.

Malicious package

livekit-agentsnpm

Malicious code in livekit-agents (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-6555

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall livekit-agents

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.

Malicious versions

3 flagged

0.3.00.3.10.3.2

Indicators of compromise (SHA-256)

5abf921f58c69745fee91e812853b493a282f3d42f55db38516ba54b827ea35b

af9fd5833a5edf24a4f6f5dbcfc23a6918928c80de2770840e50e324e995d558

e789393fbccd92c93b0b2cc8efc06e3f4a3303f8272a471941630cf3a9824fae

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for livekit-agents (3 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

No. livekit-agents on npm has been identified as a malicious package (versions 0.3.0, 0.3.1, 0.3.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007699IN-MAL-2026-007698IN-MAL-2026-007700

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.

Malware detection Runtime egress monitoring