Which versions of create-mastra are malicious?

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

How do I remediate create-mastra if I installed it?

create-mastra is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

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

If create-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 create-mastra part of a known attack campaign?

Yes — create-mastra is associated with the GHSA-jgwq-x2m5-mxhm, IN-MAL-2026-009533 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 create-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 create-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 create-mastra across your stack and pipelines.

Malicious package

create-mastranpm

create-mastra is a confirmed malicious npm package (MAL-2026-6050) that steals credentials and exfiltrates sensitive data (malicious version 1.13.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in create-mastra (npm)

MAL-2026-6050

Immediate action

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

npm uninstall create-mastra

What this malware does

create-mastra is the Mastra framework's project scaffolder, distributed as a bundled CLI. The flagged signals are generic occurrences of the literal string 'POST' across the minified dist/index.js (lines 245-247, 679, 16066) without corroborating evidence of a hardcoded attacker C2 endpoint, install-time exfiltration, or credential harvest. No install/postinstall lifecycle hooks were identified that would auto-execute network behavior on npm install. Keyword co-occurrence in a minified rollup bundle is the weakest evidence shape and is consistent with normal HTTP client code in a CLI scaffolder. Routing for human review to confirm the destinations of those POST calls are documented Mastra endpoints rather than attacker infrastructure.

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)

12df16ee90f6c59f31e4b0b71f2dbf3a0b046e17ecae5e13399b69fec9f3c563

a63f91d1b45294b3012f4a9d5cb4d90c6d52e8ef9ae3d0fea42fefa2b5d178dd

4da726670223ca28536bc00f5e68f94f22591bdecdb38dd94e5e873fce0afcf2

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for create-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 create-mastra across your stack and pipelines.
If you installed it — respond
create-mastra is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If create-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 create-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. create-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-jgwq-x2m5-mxhmIN-MAL-2026-009533

References

Credits

Amazon Inspector · finder

Detect & block this

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

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database