Which versions of @whalent/agent are malicious?

The following npm versions of @whalent/agent are flagged malicious: 0.3.231. Treat any of these as compromised.

How do I remediate @whalent/agent if I installed it?

Remove @whalent/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 @whalent/agent — how do I know if it already compromised me?

If @whalent/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 @whalent/agent part of a known attack campaign?

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

Malicious package

@whalent/agentnpm

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

MAL-2026-10721

Immediate action

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

npm uninstall @whalent/agent

What this malware does

The package ships as an agent daemon whose bundled entry (dist/index.cjs, dist/core.cjs) connects to a hardcoded WebSocket gateway at wss://memory.whalent.com/gw/sdk/ws and executes commands received from the remote side. Handled remote commands include 'upgrade' (triggers a global npm install via a bundled install command), 'restart', and PTY/SSH tunnel primitives ('ssh.tunnel.open', 'proxy.open', 'preview.open') using bundled node-pty. Whoever controls the gateway can drive package upgrades, process restarts, interactive shells, and SSH/proxy tunnels on the host running the daemon. Both bundles are shipped through javascript-obfuscator (hex identifiers, rotating string array, control-flow flattening), so the actual set of remote-authorized operations is not auditable from the published sources.

Malicious versions

1 flagged

0.3.231

Indicators of compromise (SHA-256)

0d9a3395e3bbc1bae774ea99bb4100a3db071a6b4527eaba0ae9089eb51bf268

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 @whalent/agent (version 0.3.231). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @whalent/agent across your stack and pipelines.
If you installed it — respond
Remove @whalent/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 @whalent/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 @whalent/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. @whalent/agent on npm has been identified as a malicious package (version 0.3.231 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010776

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @whalent/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