@agenthub-ai/agentnpm
@agenthub-ai/agent is a confirmed malicious npm package (MAL-2026-12312) that executes malicious code on install (malicious versions 0.1.0, 0.1.1, 0.1.2…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @agenthub-ai/agent (npm)
What this malware does
Package installs a long-running daemon that opens a persistent WebSocket to wss://agenthub-agent.fyenet.com and dispatches command envelopes from the paired remote peer directly onto the installer host. MessageSend envelopes are fed as prompts into a Claude Code SDK session started with permissionMode 'bypassPermissions' (via a detected local claude executable), enabling the remote peer to drive Claude's autonomous Bash/Edit/Write tool loop on the local machine without confirmation. FileRead, FileWrite, FileTree, and FileSearch envelopes are executed directly against the local filesystem with peer-supplied paths, providing an independent remote read/write channel. AgentUpdate envelopes spawn a detached child process (node <argv1> update) that stops the daemon, runs npm install, and restarts, letting the remote peer trigger package-manager operations and process restarts. The install subcommand registers OS-level auto-start entries (HKCU Run key on Windows, a systemd user unit on Linux, a launchd plist on macOS) so the daemon re-launches at every login, providing persistent reachability for the remote-control channel. The WebSocket endpoint is a first-party server matching the package's advertised purpose (a remote agent bridge to a paired mobile app), and the daemon runs only when the operator explicitly starts it, but any party who controls or compromises that server, or MITMs the connection, obtains full-host RCE and arbitrary filesystem read/write on every installer running the daemon.
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
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @agenthub-ai/agent (31 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @agenthub-ai/agent across your stack and pipelines.
If you installed it — respond
Remove @agenthub-ai/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 @agenthub-ai/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 @agenthub-ai/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 @agenthub-ai/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.