Which versions of mastraqqq are malicious?

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

How do I remediate mastraqqq if I installed it?

mastraqqq is a typosquat — you almost certainly intended a legitimately-named package. Remove mastraqqq, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

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

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

Yes — mastraqqq is associated with the IN-MAL-2026-006808 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 mastraqqq 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 mastraqqq (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 mastraqqq across your stack and pipelines.

Malicious package

mastraqqqnpm

mastraqqq is a confirmed malicious npm package (MAL-2026-5913) that typosquats a legitimate package to trick installs (malicious version 1.13.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in mastraqqq (npm)

MAL-2026-5913

Immediate action

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

npm uninstall mastraqqq

What this malware does

Package is published as mastraqqq but bundles a verbatim clone of the legitimate mastra CLI: the embedded package metadata declares name: "mastra", version: "1.13.0" with Mastra's homepage and repository, and the README is the upstream Mastra CLI README. The npm-published manifest under the mastraqqq name (a 3-character-suffix edit of mastra) adds a single unrelated runtime dependency, caspian-day-js@^1.11.22, which is never imported anywhere in the bundled dist/ output. Installing mastraqqq therefore silently pulls caspian-day-js — an attacker-chosen package whose contents are outside this tarball — into the consumer's install graph under cover of a Mastra impersonation. The combination of impersonation (identical bundled name/version/README/code) plus an unexplained, never-referenced extra dependency is the canonical namespace-abuse delivery shape: the lure is the typosquat, the payload arrives via the smuggled dep.

Malicious versions

1 flagged

1.13.1

Indicators of compromise (SHA-256)

6ab6891e53f407a1aebddb94c7d02dab202313f4576e37f378dfc2fc50705cd4

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for mastraqqq (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 mastraqqq across your stack and pipelines.
If you installed it — respond
mastraqqq is a typosquat — you almost certainly intended a legitimately-named package. Remove mastraqqq, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If mastraqqq 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 mastraqqq 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. mastraqqq 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

IN-MAL-2026-006808

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks mastraqqq-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