@mastra/express (npm) · Malicious Code
Affects @mastra/expressSource GCVE Database
Malicious package : remove @mastra/express and rotate any secrets on hosts that installed it.
Data as of 11 Jul 2026, 09:43 UTC
Malicious package
Published to npm · OSV MAL-2026-6022
What to do
Remove @mastra/express 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@mastra/express | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (9cd00df32d6d56cd3d4996965ed13e18c1da3a9b0007392b4fc14da1a8fcbb46) The package's bundled distribution files (dist/index.cjs and dist/index.js) contain a `Buffer.from(..., 'base64').toString('utf-8')` decode pattern. This pattern by itself is benign and extremely common in JavaScript bundles — used for inline data URIs, JWT segment parsing, encoded SVG/PNG assets, configuration constants, and similar legitimate purposes. No corroborating evidence of credential theft, exfiltration, dropper behavior, lifecycle-script abuse, or hardcoded attacker infrastructure was observed. The match is on a single keyword pattern in a bundled main module with no traced harmful execution path. ## Source: ghsa-malware (c7375ba72b0d9da5bf4d20ab526cb654b97310e39965bea22eb5d3d0557961d4) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.