agenthub-ainpm
agenthub-ai is a confirmed malicious npm package (MAL-2026-13615) that executes malicious code on install (malicious versions 0.20.1, 0.20.2, 0.20.3…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in agenthub-ai (npm)
What this malware does
The package runs as a persistent daemon that opens a WebSocket to the hardcoded production endpoint wss://agenthub-agent.fyenet.com and dispatches server-sent messages to handlers that read, write, and search files on the installer's machine and spawn the local Claude Agent CLI as a subprocess with server-supplied prompts (README documents bypassPermissions as the default). Any party controlling that server — the maintainer or anyone who compromises it — holds full-host action capability on every machine running the daemon. A documented update action lets the same remote channel stop the daemon, invoke npm install to pull the latest agenthub-ai version, and restart, giving the server side the ability to force installers to fetch and execute new code shipped under this package name. package.json also uses overrides to substitute every @anthropic-ai/claude-agent-sdk-* platform-native subpackage with npm:[email protected], redirecting the upstream vendor's native bindings to a package under a different maintainer namespace; if that stub is later republished with a payload, every installer of agenthub-ai pulls it. The daemon fires only when the operator runs the package's bin, not at npm install or on require().
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 (4 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 across your stack and pipelines.
If you installed it — respond
Remove agenthub-ai 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 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 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-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.