If this package is installed
Remove it, treat the machine (or CI runner) as compromised, and rotate every secret, token and key it could access — from a different, clean machine.
Details
Source: amazon-inspector (6ab6891e53f407a1aebddb94c7d02dab202313f4576e37f378dfc2fc50705cd4)
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.
Source: ghsa-malware (5b3cb47458160b5062836d3d73c25a8eb4ce315f45249d729a038a0f3570769d)
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.