Which versions of @agent-link/agent are malicious?

The following npm versions of @agent-link/agent are flagged malicious: 0.1.269. Treat any of these as compromised.

How do I remediate @agent-link/agent if I installed it?

Remove @agent-link/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.

I already installed @agent-link/agent — how do I know if it already compromised me?

If @agent-link/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.

Is @agent-link/agent part of a known attack campaign?

Yes — @agent-link/agent is associated with the IN-MAL-2026-010745 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 @agent-link/agent 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 @agent-link/agent (version 0.1.269). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @agent-link/agent across your stack and pipelines.

Malicious package

@agent-link/agentnpm

Malicious code in @agent-link/agent (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-10705

Immediate action

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

npm uninstall @agent-link/agent

What this malware does

The package spawns a local PTY (/bin/bash on POSIX, powershell.exe on Windows) via node-pty and wires it to a WebSocket connection that defaults to wss://msclaude.ai. In dist/connection.js, frames of type 'terminal_input' received from the relay are forwarded to terminalManager.write(data), which calls ptyProcess.write(data) in dist/terminal.js. Any party holding the session URL — including the relay operator at msclaude.ai — can send terminal_input frames that execute as arbitrary shell commands on the installer's host with the user's privileges. dist/service.js also prepends ~/.local/bin and ~/.npm-global/bin to PATH, and dist/tunnel.js issues outbound http.request calls alongside ping-based reachability checks.

Malicious versions

1 flagged

0.1.269

Indicators of compromise (SHA-256)

b3a178213d6597e731a313e9ec92f5b2afb8b955e3205500fa67ff6dc1ca989c

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 @agent-link/agent (version 0.1.269). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @agent-link/agent across your stack and pipelines.
If you installed it — respond
Remove @agent-link/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 @agent-link/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 @agent-link/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

No. @agent-link/agent on npm has been identified as a malicious package (version 0.1.269 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010745

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @agent-link/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.

Malware detection Runtime egress monitoring