Which versions of agentgui are malicious?

The following npm versions of agentgui are flagged malicious: 1.0.1127. Treat any of these as compromised.

How do I remediate agentgui if I installed it?

Remove agentgui 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.

I already installed agentgui — how do I know if it already compromised me?

If agentgui 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 agentgui part of a known attack campaign?

Yes — agentgui is associated with the GHSA-3g4v-p5hc-83qm 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 agentgui 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 agentgui (version 1.0.1127). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging agentgui across your stack and pipelines.

Malicious package

agentguinpm

agentgui is a confirmed malicious npm package (MAL-2026-14402) that executes malicious code on install (malicious version 1.0.1127). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in agentgui (npm)

MAL-2026-14402

Immediate action

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

npm uninstall agentgui

What this malware does

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

1 flagged

1.0.1127

Indicators of compromise (SHA-256)

7712e51950473497493a076fd637f14d2ba2e5a0313e9e5556f73718b34aeba6

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for agentgui (version 1.0.1127). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging agentgui across your stack and pipelines.
If you installed it — respond
Remove agentgui 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 agentgui 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 agentgui 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. agentgui on npm has been identified as a malicious package (version 1.0.1127 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-3g4v-p5hc-83qm

References

github.com

Detect & block this

O3 blocks agentgui-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database