Which versions of @mastra/stagehand are malicious?

The following npm versions of @mastra/stagehand are flagged malicious: 0.2.5. Treat any of these as compromised.

How do I remediate @mastra/stagehand if I installed it?

Remove @mastra/stagehand from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound network activity or persistence. Use O3 Security's dependency scanner to confirm the package and its artifacts are fully purged across your stack.

Is @mastra/stagehand part of a known attack campaign?

Yes — @mastra/stagehand is associated with the GHSA-x59w-qg4x-cmrx campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

Can O3 Security detect @mastra/stagehand in my codebase?

Yes. O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, blocking @mastra/stagehand and packages like it before any post-install script runs.

Malicious package

@mastra/stagehandnpm

Malicious code in @mastra/stagehand (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-6037

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @mastra/stagehand

What this malware does

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.

Malicious versions

1 flagged

0.2.5

Indicators of compromise (SHA-256)

d7fc5faac600c03f2cb3a80bc9b0d34714b5259d81a09df552fdc07f672995c0

Frequently asked questions

No. @mastra/stagehand on npm has been identified as a malicious package (version 0.2.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-x59w-qg4x-cmrx

References

github.com

Scan your dependencies

O3 Security blocks malicious packages like this at install time and in CI.

Supply-chain protection