VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

automation_model: vulnerability history, versions and safety

automation_model is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 120 releases, first recorded in Nov 2025. 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 24 Nov 2025.

See the disclosure history →
i
1 malicious-package vulnerabilities

A published version contained malicious code.

See malicious packages in npm →

See all automation_model vulnerabilities

Vulert verdict on automation_model 1.0.522 i

Updated on 23 Oct 2026

Malicious package: every vulnerability Vulert records for automation_model 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 Deprecated
  • Popularity Little adoption
  • Community Not enough data

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.0.522 — affected i
  • Vulnerabilities on record 1 over 1 year · 1 in the last year i
  • Latest disclosure 24 Nov 2025 i
  • Highest CVSS n/a i
  • With no published fix 1 i
  • Malicious packages 1 i
  • Depended on by 2 packages i
  • Last release 6 months ago i
  • Licence ISC 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 automation_model, 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
1.0.522 06 Apr 2026 C1 malicious ISC No Details →
1.0.521 31 Mar 2026 C1 malicious ISC No Details →
1.0.520 31 Mar 2026 C1 malicious ISC No Details →
1.0.519 31 Mar 2026 C1 malicious ISC No Details →
1.0.518 30 Mar 2026 C1 malicious ISC No Details →
1.0.517 30 Mar 2026 C1 malicious ISC No Details →
1.0.516 27 Mar 2026 C1 malicious ISC No Details →
1.0.932-dev 27 Mar 2026 C1 malicious ISC No Details →
1.0.931-dev 27 Mar 2026 C1 malicious ISC No Details →
1.0.930-dev 26 Mar 2026 C1 malicious ISC No Details →
1.0.929-dev 26 Mar 2026 C1 malicious ISC No Details →
1.0.515 11 Mar 2026 C1 malicious ISC No Details →
1.0.806-stage 11 Mar 2026 C1 malicious ISC No Details →
1.0.514 19 Feb 2026 C1 malicious ISC No Details →
1.0.805-stage 10 Feb 2026 C1 malicious ISC No Details →
1.0.928-dev 10 Feb 2026 C1 malicious ISC No Details →
1.0.513 02 Feb 2026 C1 malicious ISC No Details →
1.0.512 28 Jan 2026 C1 malicious ISC No Details →
1.0.804-stage 28 Jan 2026 C1 malicious ISC No Details →
1.0.927-dev 28 Jan 2026 C1 malicious ISC No Details →
1.0.926-dev 28 Jan 2026 C1 malicious ISC No Details →
1.0.511 28 Jan 2026 C1 malicious ISC No Details →
1.0.803-stage 28 Jan 2026 C1 malicious ISC No Details →
1.0.925-dev 28 Jan 2026 C1 malicious ISC No Details →
1.0.510 28 Jan 2026 C1 malicious ISC No Details →
1.0.509 28 Jan 2026 C1 malicious ISC No Details →
1.0.802-stage 28 Jan 2026 C1 malicious ISC No Details →
1.0.924-dev 28 Jan 2026 C1 malicious ISC No Details →
1.0.801-stage 28 Jan 2026 C1 malicious ISC No Details →
1.0.508 28 Jan 2026 C1 malicious ISC No Details →
1.0.923-dev 28 Jan 2026 C1 malicious ISC No Details →
1.0.507 23 Jan 2026 C1 malicious ISC No Details →
1.0.800-stage 23 Jan 2026 C1 malicious ISC No Details →
1.0.922-dev 23 Jan 2026 C1 malicious ISC No Details →
1.0.799-stage 21 Jan 2026 C1 malicious ISC No Details →
1.0.921-dev 21 Jan 2026 C1 malicious ISC No Details →
1.0.506 12 Jan 2026 C1 malicious ISC No Details →
1.0.505 07 Jan 2026 C1 malicious ISC No Details →
1.0.920-dev 30 Dec 2025 C1 malicious ISC No Details →
1.0.798-stage 30 Dec 2025 C1 malicious ISC No Details →
1.0.797-stage 29 Dec 2025 C1 malicious ISC No Details →
1.0.919-dev 29 Dec 2025 C1 malicious ISC No Details →
1.0.504 23 Dec 2025 C1 malicious ISC No Details →
1.0.503 23 Dec 2025 C1 malicious ISC No Details →
1.0.502 23 Dec 2025 C1 malicious ISC No Details →
1.0.796-stage 23 Dec 2025 C1 malicious ISC No Details →
1.0.918-dev 23 Dec 2025 C1 malicious ISC No Details →
1.0.501 22 Dec 2025 C1 malicious ISC No Details →
1.0.795-stage 22 Dec 2025 C1 malicious ISC No Details →
1.0.917-dev 22 Dec 2025 C1 malicious ISC No Details →
1.0.500 22 Dec 2025 C1 malicious ISC No Details →
1.0.794-stage 22 Dec 2025 C1 malicious ISC No Details →
1.0.916-dev 18 Dec 2025 C1 malicious ISC No Details →
1.0.499 18 Dec 2025 C1 malicious ISC No Details →
1.0.793-stage 17 Dec 2025 C1 malicious ISC No Details →
1.0.915-dev 17 Dec 2025 C1 malicious ISC No Details →
1.0.914-dev 17 Dec 2025 C1 malicious ISC No Details →
1.0.913-dev 16 Dec 2025 C1 malicious ISC No Details →
1.0.912-dev 16 Dec 2025 C1 malicious ISC No Details →
1.0.792-stage 12 Dec 2025 C1 malicious ISC No Details →
1.0.911-dev 12 Dec 2025 C1 malicious ISC No Details →
1.0.791-stage 11 Dec 2025 C1 malicious ISC No Details →
1.0.910-dev 11 Dec 2025 C1 malicious ISC No Details →
1.0.498 08 Dec 2025 C1 malicious ISC No Details →
1.0.790-stage 08 Dec 2025 C1 malicious ISC No Details →
1.0.909-dev 05 Dec 2025 C1 malicious ISC No Details →
1.0.497 05 Dec 2025 C1 malicious ISC No Details →
1.0.496 05 Dec 2025 C1 malicious ISC No Details →
1.0.789-stage 05 Dec 2025 C1 malicious ISC No Details →
1.0.788-stage 05 Dec 2025 C1 malicious ISC No Details →
1.0.908-dev 05 Dec 2025 C1 malicious ISC No Details →
1.0.907-dev 05 Dec 2025 C1 malicious ISC No Details →
1.0.787-stage 03 Dec 2025 C1 malicious ISC No Details →
1.0.906-dev 03 Dec 2025 C1 malicious ISC No Details →
1.0.905-dev 02 Dec 2025 C1 malicious ISC No Details →
1.0.904-dev 02 Dec 2025 C1 malicious ISC No Details →
1.0.903-dev 02 Dec 2025 C1 malicious ISC No Details →
1.0.902-dev 01 Dec 2025 C1 malicious ISC No Details →
1.0.901-dev 01 Dec 2025 C1 malicious ISC No Details →
1.0.900-dev 01 Dec 2025 C1 malicious ISC No Details →
1.0.899-dev 30 Nov 2025 C1 malicious ISC No Details →
1.0.898-dev 30 Nov 2025 C1 malicious ISC No Details →
1.0.495 28 Nov 2025 C1 malicious ISC No Details →
1.0.786-stage 28 Nov 2025 C1 malicious ISC No Details →
1.0.785-stage 28 Nov 2025 C1 malicious ISC No Details →
1.0.494 27 Nov 2025 C1 malicious ISC No Details →
1.0.784-stage 27 Nov 2025 C1 malicious ISC No Details →
1.0.783-stage 25 Nov 2025 C1 malicious ISC No Details →
1.0.493 25 Nov 2025 C1 malicious ISC No Details →
1.0.897-dev 24 Nov 2025 C1 malicious ISC No Details →
1.0.782-stage 24 Nov 2025 C1 malicious ISC No Details →
1.0.492 24 Nov 2025 C1 malicious ISC No Details →
1.0.896-dev 24 Nov 2025 C1 malicious ISC No Details →
1.0.490 20 Nov 2025 C1 malicious ISC No Details →
1.0.780-stage 17 Nov 2025 C1 malicious ISC No Details →
1.0.894-dev 17 Nov 2025 C1 malicious ISC No Details →
1.0.779-stage 17 Nov 2025 C1 malicious ISC No Details →
1.0.893-dev 17 Nov 2025 C1 malicious ISC No Details →
1.0.489 14 Nov 2025 C1 malicious ISC No Details →
1.0.892-dev 13 Nov 2025 C1 malicious ISC No Details →
1.0.488 12 Nov 2025 C1 malicious — No Details →
1.0.778-stage 12 Nov 2025 C1 malicious — No Details →
1.0.891-dev 12 Nov 2025 C1 malicious — No Details →
1.0.777-stage 10 Nov 2025 C1 malicious — No Details →
1.0.776-stage 10 Nov 2025 C1 malicious — No Details →
1.0.890-dev 09 Nov 2025 C1 malicious — No Details →
1.0.775-stage 07 Nov 2025 C1 malicious — No Details →
1.0.889-dev 07 Nov 2025 C1 malicious — No Details →
1.0.774-stage 31 Oct 2025 C1 malicious — No Details →
1.0.888-dev 31 Oct 2025 C1 malicious — No Details →
1.0.487 30 Oct 2025 C1 malicious — No Details →
1.0.773-stage 28 Oct 2025 C1 malicious — No Details →
1.0.772-stage 28 Oct 2025 C1 malicious — No Details →
1.0.887-dev 28 Oct 2025 C1 malicious — No Details →
1.0.886-dev 28 Oct 2025 C1 malicious — No Details →
1.0.486 28 Oct 2025 C1 malicious — No Details →
1.0.771-stage 28 Oct 2025 C1 malicious — No Details →
1.0.885-dev 28 Oct 2025 C1 malicious — No Details →
1.0.770-stage 27 Oct 2025 C1 malicious — No Details →
1.0.884-dev 26 Oct 2025 C1 malicious — No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 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 automation_model

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 automation_model Package N/A critical No fix published 24 Nov 2025

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 automation_model

Is automation_model safe to use?

No. Vulert records a malicious-package vulnerability for automation_model: 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 automation_model's Vulert package health score?

Vulert scores automation_model 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 automation_model affected?

Yes. 1.0.522, 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.

Which version of automation_model should I use?

1.0.522 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does automation_model have?

1 vulnerability is recorded for automation_model 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 automation_model vulnerabilities disclosed?

1 vulnerability was recorded for automation_model in the last 12 months, and the oldest entry in this database dates to 24 Nov 2025. 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 automation_model 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 automation_model for upcoming vulnerabilities?

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