# MAL-2026-10721: Malicious code in @whalent/agent (npm)


- **Type:** Malicious package
- **Package:** `@whalent/agent` (npm)
- **Published:** 16 Jul 2026

## What is MAL-2026-10721?

MAL-2026-10721 is a malicious package in @whalent/agent, published on 16 Jul 2026. 

### Official description

The package installs a `whalent` CLI daemon that opens a persistent WebSocket connection (`wss://`) to a Whalent Memory gateway and, per its own README, accepts remote commands including 'upgrade' and 'restart' from that gateway. `dist/index.cjs` contains an `npmInstallCommand` builder that assembles `npm install -g @whalent/agent@<version> --registry=<DEFAULT_NPM_REGISTRY|CHINA_NPM_REGISTRY>` strings driven by the gateway's chosen version — meaning whoever controls (or compromises) the gateway can cause the daemon's host to install and execute an arbitrary version of the package as the user running the daemon. The core bundle additionally references `process.env.SHELL` and localhost RDP/VNC ports (127.0.0.1:3389, 5900, 5901), and the dependency set includes `@xterm/headless`, `node-pty` (optional), `ssh2`, and `ws`, indicating terminal/PTY and remote-session capability reachable from the same gateway channel. Both `dist/index.cjs` (main/bin entry) and the 13 MB `dist/core.cjs` are transformed with javascript-obfuscator (string-array rotator, `_0x`-named helpers, control-flow flattening), and `javascript-obfuscator` is listed in devDependencies — the obfuscation covers the gateway command dispatcher and shell sinks. The daemon fires only when the operator explicitly runs `whalent --token …`, not on `npm install` or on `require()`, but once running it provides a network-reachable code-execution and shell surface on the host controlled by the gateway operator.

## What should I do about MAL-2026-10721?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-10721 is a malicious package: @whalent/agent (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-10721/ (Markdown: https://insights.sbomify.com/MAL-2026-10721/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-10721

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-10721/
Summaries are generated and may contain mistakes; the official description above is the record.