@whalent/agent-core (npm) · Malicious Code
Affects @whalent/agent-coreSource GCVE Database
Malicious package : remove @whalent/agent-core and rotate any secrets on hosts that installed it.
Data as of 26 Oct 2026, 16:15 UTC
Malicious package
Published to npm · OSV MAL-2026-10722
What to do
Remove @whalent/agent-core 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-core | Affected
| 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-core npm package contains malicious code that establishes a WebSocket connection to a hardcoded remote gateway, enabling the operator to execute arbitrary commands on any host running the package. The package supports remote code updates from the same gateway without visible version or signature verification. It also exfiltrates AI-provider session identifiers and API keys to the attacker-controlled host. The code is heavily obfuscated to evade casual inspection. This affects specific versions of the package and no official patch or fix is currently documented.
References
- npmjs.com/package/@whalent/agent-core/v/0.3.230 (opens in a new tab)
- npmjs.com/package/@whalent/agent-core/v/0.3.231 (opens in a new tab)
- npmjs.com/package/@whalent/agent-core/v/0.3.232 (opens in a new tab)
- npmjs.com/package/@whalent/agent-core/v/0.3.233 (opens in a new tab)
- npmjs.com/package/@whalent/agent-core/v/0.3.254 (opens in a new tab)
- npmjs.com/package/@whalent/agent-core/v/0.3.280 (opens in a new tab)
- npmjs.com/package/@whalent/agent-core/v/0.3.298 (opens in a new tab)
- npmjs.com/package/@whalent/agent-core/v/0.3.294 (opens in a new tab)
- npmjs.com/package/@whalent/agent-core/v/0.3.295 (opens in a new tab)
- npmjs.com/package/@whalent/agent-core/v/0.3.277 (opens in a new tab)
- npmjs.com/package/@whalent/agent-core/v/0.3.278 (opens in a new tab)
- npmjs.com/package/@whalent/agent-core/v/0.3.282 (opens in a new tab)
- npmjs.com/package/@whalent/agent-core/v/0.3.276 (opens in a new tab)
- npmjs.com/package/@whalent/agent-core/v/0.3.296 (opens in a new tab)
- npmjs.com/package/@whalent/agent-core/v/0.3.275 (opens in a new tab)
- npmjs.com/package/@whalent/agent-core/v/0.3.271 (opens in a new tab)
- npmjs.com/package/@whalent/agent-core/v/0.3.297 (opens in a new tab)
- npmjs.com/package/@whalent/agent-core/v/0.3.291 (opens in a new tab)
- npmjs.com/package/@whalent/agent-core/v/0.3.289 (opens in a new tab)
- npmjs.com/package/@whalent/agent-core/v/0.3.273 (opens in a new tab)