Which versions of @mastra/convex are malicious?

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

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

Remove @mastra/convex 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/convex — how do I know if it already compromised me?

If @mastra/convex was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

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

Yes — @mastra/convex is associated with the GHSA-3g98-f7ww-r9qq, IN-MAL-2026-008463 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/convex across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @mastra/convex (version 1.2.2).

Part of a larger attack: @mastra published 89 malicious packages. See the full campaign →

Malicious package

@mastra/convexnpm

Advisory published Jun 17, 2026Updated Jul 8, 2026

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

Malicious code in @mastra/convex (npm)

MAL-2026-6010

Immediate action

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

npm uninstall @mastra/convex

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.2.2

Indicators of compromise (SHA-256)

acae13d27edf4e66aa693ee00ce3df3eb508a09c9bf7a9b934a9d3804653f3ce

41dfa2c64fb78e90a91f5e548a6ed50f1d45ad18ec398d5faba1d71f1c53ff2f

2f203e86af09c48bcbd9f0751ff22096ff2c53d4982f2482031dc3d0d161434b

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @mastra/convex (version 1.2.2).
If you installed it — respond
Remove @mastra/convex 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/convex was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

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

Campaign

GHSA-3g98-f7ww-r9qqIN-MAL-2026-008463

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @mastra/convex-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