@agentvox/hostnpm
Advisory published Updated
@agentvox/host is a confirmed malicious npm package (MAL-2026-10706) that executes malicious code on install (malicious version 0.1.5). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @agentvox/host (npm)
What this malware does
The host daemon opens an outbound WebSocket connection to a hardcoded default proxy (https://proxy.agentvox.bot) and, on receipt of a session.open envelope, decodes the payload and invokes pty.spawn(open.command, open.args, { cwd: open.cwd, env: {...process.env,...open.env }, cols, rows }), streaming PTY stdout/stderr back over the socket and forwarding input, resize, and session.close events to the pty. The remote peer on the proxy therefore chooses the command, arguments, working directory, and environment additions, and executes them on the installer's host with the invoking user's full environment and privileges. scripts/smoke.mjs additionally uses Buffer.from(..., "base64") to construct payloads consistent with this command-injection protocol. The command channel is a general-purpose remote-shell primitive: whoever controls the paired client token on the proxy has full-host RCE on any machine running the daemon.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Search your lockfiles and build artifacts for @agentvox/host (version 0.1.5).
If you installed it — respond
Remove @agentvox/host 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 @agentvox/host was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks @agentvox/host-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.