@vanexalabs-ai/vanexa-agentnpm
@vanexalabs-ai/vanexa-agent is a confirmed malicious npm package (MAL-2026-13397) that executes malicious code on install (malicious versions 1.3.50, 1.3.51, 1.3.52…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @vanexalabs-ai/vanexa-agent (npm)
What this malware does
The package implements a daemon that pairs with a remote peer (phone) over WebRTC, using https://vanexa-agent-relay.workers.dev and https://vanexa-agent-relay.tubefood.workers.dev as signaling relays, and executes commands received over the DataChannel by dispatching them into child_process.spawn/exec on the host running the agent. onData/onCommand/onmessage handlers are wired to shell/exec sinks in dist/bundle.cjs (POST calls at lines 221, 285, 426, 1953, 2101 correspond to signaling traffic). Anyone who controls the signaling relay or a paired peer obtains full-host remote code execution on the machine running the agent. The runtime dispatch logic is shipped only as V8 bytecode (dist/bundle.jsc loaded via bytenode from bin/vanexa-agent.js), with the.cjs fallback minified, framed in the README as 'commercial IP protection' — pairing/authorization semantics are not reviewable from source. A socket.json at the tarball root sets 'ignore' for aiMalware, gptMalware, obfuscatedCode, usesEval, nativeCode, shellAccess, filesystemAccess, networkAccess, bypassesEnvironment, and installScripts — a blanket suppression matching exactly the categories this package's runtime behavior triggers. The shell surface fires when the operator explicitly runs the agent (not at npm install or on require), so blast radius is bounded to hosts where an operator starts the daemon and completes pairing; however, once running, the remote peer channel is the attack surface.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @vanexalabs-ai/vanexa-agent (12 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @vanexalabs-ai/vanexa-agent across your stack and pipelines.
If you installed it — respond
Remove @vanexalabs-ai/vanexa-agent from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If @vanexalabs-ai/vanexa-agent 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 @vanexalabs-ai/vanexa-agent 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 @vanexalabs-ai/vanexa-agent-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.