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.

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.

No official patch or remediation is currently documented. 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. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance.