MalwarePublished 16 Jul 2026Updated 6 Aug 2026

@whalent/agent (npm) · Malicious Code

Affects @whalent/agentSource GCVE Database

Malicious package : remove @whalent/agent and rotate any secrets on hosts that installed it.

Data as of 6 Aug 2026, 18:46 UTC

Classification

Malicious package

Published to npm · OSV MAL-2026-10721

What to do

Remove @whalent/agent from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.

Affected software

Product	Affected	Fixed in
npm@whalent/agent	Affected 0.3.230 – 0.3.302 41 affected builds	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

The @whalent/agent npm package installs a CLI daemon that establishes a persistent WebSocket connection to a remote Whalent Memory gateway. This daemon accepts remote commands, including the ability to upgrade or restart itself by installing arbitrary package versions as directed by the gateway operator. The package includes obfuscated JavaScript code enabling remote code execution and shell access on the host machine when the daemon is explicitly started by the user. The daemon does not activate on installation or import but only when run with a specific token. Multiple specific versions of the package are affected.

Impact

An attacker controlling or compromising the Whalent Memory gateway can remotely execute arbitrary code on any host running the @whalent/agent daemon. This includes installing arbitrary package versions, restarting the daemon, and accessing local terminal sessions and remote desktop ports. The compromise can lead to full host control under the daemon's user context. The malicious functionality is dormant until the daemon is explicitly started, reducing accidental detection but enabling persistent remote control once active.

Defensive guidance

Users should avoid running the @whalent/agent daemon, especially with tokens that activate its remote control features. Since the daemon only activates when explicitly run, do not execute the 'whalent --token ...' command or any related binaries from this package. Monitor for and remove any installations of the affected package versions. Check vendor advisories or npm security notices for updates or official guidance.

Summary

The @whalent/agent package contains a malicious CLI daemon that connects to a remote gateway over a secure WebSocket. The gateway can issue commands to the daemon, including upgrading the package version via npm install commands constructed dynamically, allowing arbitrary code execution as the user running the daemon. The package references local RDP/VNC ports and includes dependencies supporting terminal and remote session capabilities, indicating potential for remote shell access. The core code is heavily obfuscated, complicating analysis and detection. The daemon only activates when explicitly run with a token, not on installation or import, providing a stealthy persistence mechanism controlled remotely.

References

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 6 Aug 2026, 18:46 UTC

Technical details

References

Community reviews