Which versions of @mastra/rag are malicious?

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

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

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

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

Yes — @mastra/rag is associated with the GHSA-442j-fj4w-jhpw, IN-MAL-2026-008315 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/rag 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/rag (version 2.2.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @mastra/rag across your stack and pipelines.

Malicious package

@mastra/ragnpm

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

Malicious code in @mastra/rag (npm)

MAL-2026-5961

Immediate action

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

npm uninstall @mastra/rag

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

2.2.2

Indicators of compromise (SHA-256)

e9608d74e59d524d1052f6b05c8fba2b9d181452f28a012785eb80cb6764abe3

becdc7029b48fd8b806ea128f586d07425dcde31dddf26ca7748ed447593f5f6

031ec31035fa78e914e64884be3019150c8f1f77b9c464bce74e63cb0cd13227

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/rag (version 2.2.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @mastra/rag across your stack and pipelines.
If you installed it — respond
Remove @mastra/rag 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/rag 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/rag 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/rag on npm has been identified as a malicious package (version 2.2.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-442j-fj4w-jhpwIN-MAL-2026-008315

References

Credits

Amazon Inspector · finder

Detect & block this

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