Which versions of mastra are malicious?

The following npm versions of mastra are flagged malicious: 1.13.1. Treat any of these as compromised.

How do I remediate mastra if I installed it?

Remove mastra 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 activity or persistence.

I already installed mastra — how do I know if it already compromised me?

If mastra was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is mastra part of a known attack campaign?

Yes — mastra is associated with the GHSA-mvf4-vg87-q9vm, IN-MAL-2026-008558 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find mastra across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for mastra (version 1.13.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging mastra across your stack and pipelines.

Malicious package

mastranpm

mastra is a confirmed malicious npm package (MAL-2026-5965) that executes malicious code on install (malicious version 1.13.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in mastra (npm)

MAL-2026-5965

Immediate action

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

npm uninstall mastra

What this malware does

The package was found to contain malicious code or consuming dependency that contains malicious code

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

1.13.1

Indicators of compromise (SHA-256)

177b60c8d45a21867d69c269f21c334505b8c0298b497cbed321d403be4311f7

bd7e724f9b33f25021b1da14adbe9c148b2df1addc912f98a372e1a4f486308e

74c4549467abc2b76f088b4684a79cb551458718b7c5d9beb8ae1af4349d02a8

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for mastra (version 1.13.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging mastra across your stack and pipelines.
If you installed it — respond
Remove mastra 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 activity or persistence.
Did it already run?
If mastra was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks mastra before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

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

Campaign

GHSA-mvf4-vg87-q9vmIN-MAL-2026-008558

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks mastra-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database