VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@mastra/core: vulnerability history, versions and safety

@mastra/core is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 120 releases, first recorded in Jun 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded C1
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
1 in the last 12 months

Most recent disclosure 17 Jun 2026.

See the disclosure history →
i
1 malicious-package vulnerabilities

A published version contained malicious code.

See malicious packages in npm →

See all @mastra/core vulnerabilities

Vulert verdict on @mastra/core 1.79.0 i

Updated on 23 Oct 2026

Malicious package: every vulnerability Vulert records for @mastra/core is a malicious-package vulnerability — a published version contained hostile code rather than a bug. Do not install it, and check whether it is already resolved in your dependencies.

Package health score 15/100
  • Security Malicious code published
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Active

The current release contains malicious code, which caps this score.

What to do: Do not install this package. If it is already in your dependency tree, remove or replace it, and check what resolved it in the first place. Vulert keeps watching the name: if a maintained replacement appears, you will see it here. Monitor it with Vulert →

  • Current release 1.79.0 — affected i
  • Vulnerabilities on record 1 over 1 year · 1 in the last year i
  • Latest disclosure 17 Jun 2026 i
  • Highest CVSS n/a i
  • With no published fix 1 i
  • Malicious packages 1 i
  • Depended on by 206 packages i
  • Stars 28,834 i
  • Last release this month i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for @mastra/core, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
0.0.0-playground-snapshot-20261022163221 22 Oct 2026 C1 malicious Apache-2.0 No Details →
0.0.0-playground-snapshot-20261022-165632-20261022150100 22 Oct 2026 C1 malicious Apache-2.0 No Details →
0.0.0-test-mastra-doctor-snapshot-2026-10-21-20261021192403 21 Oct 2026 C1 malicious Apache-2.0 No Details →
0.0.0-main-20261021-185838-20261021190159 21 Oct 2026 C1 malicious Apache-2.0 No Details →
0.0.0-max-metrics-charts-gateway-20261021122623 21 Oct 2026 C1 malicious Apache-2.0 No Details →
1.79.0 21 Oct 2026 C1 malicious Apache-2.0 No Details →
0.0.0-playground-snapshot-20261021-20261021110449 21 Oct 2026 C1 malicious Apache-2.0 No Details →
0.0.0-main-20261021-095050-20261021075405 21 Oct 2026 C1 malicious Apache-2.0 No Details →
1.79.0-alpha.12 21 Oct 2026 C1 malicious Apache-2.0 No Details →
1.79.0-alpha.11 20 Oct 2026 C1 malicious Apache-2.0 No Details →
1.79.0-alpha.10 20 Oct 2026 C1 malicious Apache-2.0 No Details →
1.79.0-alpha.9 20 Oct 2026 C1 malicious Apache-2.0 No Details →
0.0.0-pre-v1-beta-20261020162952 20 Oct 2026 C1 malicious Apache-2.0 No Details →
0.0.0-playground-snapshot-20261020-20261020151708 20 Oct 2026 C1 malicious Apache-2.0 No Details →
1.79.0-alpha.8 20 Oct 2026 C1 malicious Apache-2.0 No Details →
1.79.0-alpha.7 20 Oct 2026 C1 malicious Apache-2.0 No Details →
1.79.0-alpha.6 20 Oct 2026 C1 malicious Apache-2.0 No Details →
1.79.0-alpha.5 19 Oct 2026 C1 malicious Apache-2.0 No Details →
1.79.0-alpha.4 19 Oct 2026 C1 malicious Apache-2.0 No Details →
0.0.0-playground-main-20261019182229 19 Oct 2026 C1 malicious Apache-2.0 No Details →
0.0.0-obs-567-obs-666-20261019081448 19 Oct 2026 C1 malicious Apache-2.0 No Details →
0.0.0-obs-567-add-to-dataset-20261019081158 19 Oct 2026 C1 malicious Apache-2.0 No Details →
0.0.0-avatar-inline-obs-666-20261018210608 18 Oct 2026 C1 malicious Apache-2.0 No Details →
0.0.0-avatar-inline-obs-666-20261018204602 18 Oct 2026 C1 malicious Apache-2.0 No Details →
0.0.0-avatar-inline-size-20261018203451 18 Oct 2026 C1 malicious Apache-2.0 No Details →
1.79.0-alpha.3 17 Oct 2026 C1 malicious Apache-2.0 No Details →
1.79.0-alpha.2 16 Oct 2026 C1 malicious Apache-2.0 No Details →
0.0.0-obs-666-group-by-20261016174001 16 Oct 2026 C1 malicious Apache-2.0 No Details →
0.0.0-obs-666-group-by-20261016165435 16 Oct 2026 C1 malicious Apache-2.0 No Details →
1.79.0-alpha.1 16 Oct 2026 C1 malicious Apache-2.0 No Details →
1.78.1-alpha.0 16 Oct 2026 C1 malicious Apache-2.0 No Details →
1.78.0 15 Oct 2026 C1 malicious Apache-2.0 No Details →
1.78.0-alpha.9 15 Oct 2026 C1 malicious Apache-2.0 No Details →
0.0.0-playground-main-20261015184815 15 Oct 2026 C1 malicious Apache-2.0 No Details →
0.0.0-aggregate-trace-20261015182851 15 Oct 2026 C1 malicious Apache-2.0 No Details →
1.78.0-alpha.8 15 Oct 2026 C1 malicious Apache-2.0 No Details →
1.78.0-alpha.7 15 Oct 2026 C1 malicious Apache-2.0 No Details →
1.78.0-alpha.6 15 Oct 2026 C1 malicious Apache-2.0 No Details →
1.78.0-alpha.5 15 Oct 2026 C1 malicious Apache-2.0 No Details →
1.78.0-alpha.4 15 Oct 2026 C1 malicious Apache-2.0 No Details →
1.78.0-alpha.3 15 Oct 2026 C1 malicious Apache-2.0 No Details →
1.78.0-alpha.2 14 Oct 2026 C1 malicious Apache-2.0 No Details →
1.78.0-alpha.1 14 Oct 2026 C1 malicious Apache-2.0 No Details →
1.78.0-alpha.0 14 Oct 2026 C1 malicious Apache-2.0 No Details →
1.77.0 14 Oct 2026 C1 malicious Apache-2.0 No Details →
1.77.0-alpha.4 14 Oct 2026 C1 malicious Apache-2.0 No Details →
0.0.0-factory-auth-20261013175540 13 Oct 2026 C1 malicious Apache-2.0 No Details →
1.77.0-alpha.3 13 Oct 2026 C1 malicious Apache-2.0 No Details →
0.0.0-playground-main-20261013-20261013064257 13 Oct 2026 C1 malicious Apache-2.0 No Details →
1.77.0-alpha.2 13 Oct 2026 C1 malicious Apache-2.0 No Details →
1.77.0-alpha.1 12 Oct 2026 C1 malicious Apache-2.0 No Details →
1.77.0-alpha.0 12 Oct 2026 C1 malicious Apache-2.0 No Details →
1.76.0 11 Oct 2026 C1 malicious Apache-2.0 No Details →
1.76.0-alpha.9 11 Oct 2026 C1 malicious Apache-2.0 No Details →
1.76.0-alpha.8 11 Oct 2026 C1 malicious Apache-2.0 No Details →
0.0.0-om-lifecycle-20261010194955 10 Oct 2026 C1 malicious Apache-2.0 No Details →
1.76.0-alpha.7 10 Oct 2026 C1 malicious Apache-2.0 No Details →
1.76.0-alpha.6 10 Oct 2026 C1 malicious Apache-2.0 No Details →
0.0.0-factory-auth-20261009225548 09 Oct 2026 C1 malicious Apache-2.0 No Details →
0.0.0-factory-auth-20261009213754 09 Oct 2026 C1 malicious Apache-2.0 No Details →
1.76.0-alpha.5 09 Oct 2026 C1 malicious Apache-2.0 No Details →
1.76.0-alpha.4 09 Oct 2026 C1 malicious Apache-2.0 No Details →
0.0.0-disclosure-chevron-20261009130749 09 Oct 2026 C1 malicious Apache-2.0 No Details →
0.0.0-metrics-y-axis-20261009082604 09 Oct 2026 C1 malicious Apache-2.0 No Details →
0.0.0-knowledge-w2-demo-20261009074925 09 Oct 2026 C1 malicious Apache-2.0 No Details →
0.0.0-knowledge-w1-20261009054256 09 Oct 2026 C1 malicious Apache-2.0 No Details →
0.0.0-knowledge-w1-20261009044833 09 Oct 2026 C1 malicious Apache-2.0 No Details →
1.76.0-alpha.3 09 Oct 2026 C1 malicious Apache-2.0 No Details →
0.0.0-knowledge-w1-20261009040610 09 Oct 2026 C1 malicious Apache-2.0 No Details →
0.0.0-knowledge-w1-20261009033246 09 Oct 2026 C1 malicious Apache-2.0 No Details →
0.0.0-knowledge-w1-20261008225219 08 Oct 2026 C1 malicious Apache-2.0 No Details →
0.0.0-fix-set-cookie-20261008222303 08 Oct 2026 C1 malicious Apache-2.0 No Details →
0.0.0-knowledge-w1-20261008204450 08 Oct 2026 C1 malicious Apache-2.0 No Details →
0.0.0-fix-set-cookie-20261008203114 08 Oct 2026 C1 malicious Apache-2.0 No Details →
0.0.0-om-lifecycle-20261008200611 08 Oct 2026 C1 malicious Apache-2.0 No Details →
0.0.0-metrics-usageId-20261008200434 08 Oct 2026 C1 malicious Apache-2.0 No Details →
0.0.0-om-lifecycle-20261008193208 08 Oct 2026 C1 malicious Apache-2.0 No Details →
1.76.0-alpha.2 08 Oct 2026 C1 malicious Apache-2.0 No Details →
0.0.0-fix-set-cookie-20261008170415 08 Oct 2026 C1 malicious Apache-2.0 No Details →
1.76.0-alpha.1 08 Oct 2026 C1 malicious Apache-2.0 No Details →
0.0.0-knowledge-w2-20261008040304 08 Oct 2026 C1 malicious Apache-2.0 No Details →
0.0.0-knowledge-w1-20261007232522 08 Oct 2026 C1 malicious Apache-2.0 No Details →
0.0.0-knowledge-w2-20261007223745 07 Oct 2026 C1 malicious Apache-2.0 No Details →
0.0.0-knowledge-w2-20261007195847 07 Oct 2026 C1 malicious Apache-2.0 No Details →
1.76.0-alpha.0 07 Oct 2026 C1 malicious Apache-2.0 No Details →
0.0.0-playground-snapshot-20261007-20261007145206 07 Oct 2026 C1 malicious Apache-2.0 No Details →
0.0.0-charts-polish-20261007113117 07 Oct 2026 C1 malicious Apache-2.0 No Details →
1.75.0 07 Oct 2026 C1 malicious Apache-2.0 No Details →
0.0.0-om-budget-isolated-20261007043742 07 Oct 2026 C1 malicious Apache-2.0 No Details →
1.75.0-alpha.8 07 Oct 2026 C1 malicious Apache-2.0 No Details →
0.0.0-om-lifecycle-20261007040229 07 Oct 2026 C1 malicious Apache-2.0 No Details →
0.0.0-om-lifecycle-20261006213520 06 Oct 2026 C1 malicious Apache-2.0 No Details →
0.0.0-stove-pageantic-20261006161243 06 Oct 2026 C1 malicious Apache-2.0 No Details →
0.0.0-playground-snapshot-20261006-095009-20261006075314 06 Oct 2026 C1 malicious Apache-2.0 No Details →
1.75.0-alpha.6 06 Oct 2026 C1 malicious Apache-2.0 No Details →
0.0.0-knowledge-w1-20261006001735 06 Oct 2026 C1 malicious Apache-2.0 No Details →
1.75.0-alpha.5 05 Oct 2026 C1 malicious Apache-2.0 No Details →
1.75.0-alpha.4 05 Oct 2026 C1 malicious Apache-2.0 No Details →
0.0.0-react-sdk-20261005160725 05 Oct 2026 C1 malicious Apache-2.0 No Details →
0.0.0-feat-charts-polish-20261005132302 05 Oct 2026 C1 malicious Apache-2.0 No Details →
1.75.0-alpha.3 03 Oct 2026 C1 malicious — No Details →
1.75.0-alpha.2 03 Oct 2026 C1 malicious — No Details →
1.75.0-alpha.1 02 Oct 2026 C1 malicious — No Details →
0.0.0-polyester-catcher-20261002131924 02 Oct 2026 C1 malicious — No Details →
0.0.0-marvin-deploy-trace-e-20261002114957 02 Oct 2026 C1 malicious — No Details →
1.75.0-alpha.0 02 Oct 2026 C1 malicious — No Details →
1.74.0 01 Oct 2026 C1 malicious — No Details →
1.73.1-alpha.1 01 Oct 2026 C1 malicious — No Details →
1.73.1-alpha.0 01 Oct 2026 C1 malicious — No Details →
0.0.0-marvin-deploy-trace-d-20261001094745 01 Oct 2026 C1 malicious — No Details →
1.73.0 01 Oct 2026 C1 malicious — No Details →
0.0.0-marvin-deploy-trace-c-20261001065356 01 Oct 2026 C1 malicious — No Details →
1.73.0-alpha.1 01 Oct 2026 C1 malicious — No Details →
1.73.0-alpha.0 30 Sep 2026 C1 malicious — No Details →
0.0.0-feat-mcp-typegen-20260930124658 30 Sep 2026 C1 malicious — No Details →
0.0.0-marvin-deploy-trace-b-20260930122039 30 Sep 2026 C1 malicious — No Details →
0.0.0-fix-studio-trace-thread-hide-om-20260930091934 30 Sep 2026 C1 malicious — No Details →
0.0.0-marvin-deploy-traces-a-20260930070026 30 Sep 2026 C1 malicious — No Details →
1.72.0 30 Sep 2026 C1 malicious — No Details →
1.72.0-alpha.10 29 Sep 2026 C1 malicious — No Details →

The newest 120 of 1,742 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 1 of the 1 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for @mastra/core

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Critical Malicious Code Vulnerability in @mastra/core Package N/A critical No fix published 17 Jun 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About @mastra/core

Is @mastra/core safe to use?

No. Vulert records a malicious-package vulnerability for @mastra/core: a published version contained hostile code rather than a bug, and the package looks like one that was withdrawn for abuse. Do not install it, and check whether it is already resolved in your dependencies.

What is @mastra/core's Vulert package health score?

Vulert scores @mastra/core 15/100, which reads as critical. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The current release contains malicious code, which caps this score.

Is the latest version of @mastra/core affected?

Yes. 1.79.0, the version you would install today, has 1 known vulnerability, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

How many vulnerabilities does @mastra/core have?

1 vulnerability is recorded for @mastra/core in the npm ecosystem: 1 critical, 0 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new @mastra/core vulnerabilities disclosed?

1 vulnerability was recorded for @mastra/core in the last 12 months, and the oldest entry in this database dates to 17 Jun 2026. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of @mastra/core are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

What does a malicious-package vulnerability mean?

It means the published package itself contained hostile code — a backdoor, a credential stealer or similar — rather than only a bug. Registries remove such packages once they are confirmed, so treat any application that resolved an affected version as compromised and rotate the credentials it could reach.

How do I monitor @mastra/core for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the @mastra/core version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.