VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@dev-blinq/ui-systems: vulnerability history, versions and safety

@dev-blinq/ui-systems 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 25 Nov 2025.

See the disclosure history →
i
1 malicious-package vulnerabilities

A published version contained malicious code.

See malicious packages in npm →

See all @dev-blinq/ui-systems vulnerabilities

Vulert verdict on @dev-blinq/ui-systems 1.0.151 i

Updated on 23 Oct 2026

Malicious package: every vulnerability Vulert records for @dev-blinq/ui-systems 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 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.151 — affected i
  • Vulnerabilities on record 1 over 1 year · 1 in the last year i
  • Latest disclosure 25 Nov 2025 i
  • Highest CVSS n/a i
  • With no published fix 1 i
  • Malicious packages 1 i
  • Last release 8 months ago 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 @dev-blinq/ui-systems, 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.151 13 Feb 2026 C1 malicious — No Details →
1.0.150 21 Jan 2026 C1 malicious — No Details →
1.0.149 16 Jan 2026 C1 malicious — No Details →
1.0.148 13 Jan 2026 C1 malicious — No Details →
1.0.147 13 Jan 2026 C1 malicious — No Details →
1.0.146 13 Jan 2026 C1 malicious — No Details →
1.0.145 12 Jan 2026 C1 malicious — No Details →
1.0.144 12 Jan 2026 C1 malicious — No Details →
1.0.143 12 Jan 2026 C1 malicious — No Details →
1.0.142 12 Jan 2026 C1 malicious — No Details →
1.0.141 12 Jan 2026 C1 malicious — No Details →
1.0.140 12 Jan 2026 C1 malicious — No Details →
1.0.139 09 Jan 2026 C1 malicious — No Details →
1.0.138 05 Jan 2026 C1 malicious — No Details →
1.0.137 30 Dec 2025 C1 malicious — No Details →
1.0.136 30 Dec 2025 C1 malicious — No Details →
1.0.135 29 Dec 2025 C1 malicious — No Details →
1.0.134 26 Dec 2025 C1 malicious — No Details →
1.0.133 24 Dec 2025 C1 malicious — No Details →
1.0.132 19 Dec 2025 C1 malicious — No Details →
1.0.131 18 Dec 2025 C1 malicious — No Details →
1.0.130 17 Dec 2025 C1 malicious — No Details →
1.0.129 17 Dec 2025 C1 malicious — No Details →
1.0.128 17 Dec 2025 C1 malicious — No Details →
1.0.127 17 Dec 2025 C1 malicious — No Details →
1.0.126 16 Dec 2025 C1 malicious — No Details →
1.0.125 16 Dec 2025 C1 malicious — No Details →
1.0.124 15 Dec 2025 C1 malicious — No Details →
1.0.123 15 Dec 2025 C1 malicious — No Details →
1.0.122 15 Dec 2025 C1 malicious — No Details →
1.0.121 15 Dec 2025 C1 malicious — No Details →
1.0.120 15 Dec 2025 C1 malicious — No Details →
1.0.119 15 Dec 2025 C1 malicious — No Details →
1.0.118 15 Dec 2025 C1 malicious — No Details →
1.0.117 12 Dec 2025 C1 malicious — No Details →
1.0.116 12 Dec 2025 C1 malicious — No Details →
1.0.115 12 Dec 2025 C1 malicious — No Details →
1.0.114 12 Dec 2025 C1 malicious — No Details →
1.0.113 12 Dec 2025 C1 malicious — No Details →
1.0.112 11 Dec 2025 C1 malicious — No Details →
1.0.111 11 Dec 2025 C1 malicious — No Details →
1.0.110 09 Dec 2025 C1 malicious — No Details →
1.0.109 08 Dec 2025 C1 malicious — No Details →
1.0.108 08 Dec 2025 C1 malicious — No Details →
1.0.107 03 Dec 2025 C1 malicious — No Details →
1.0.106 01 Dec 2025 C1 malicious — No Details →
1.0.105 28 Nov 2025 C1 malicious — No Details →
1.0.104 28 Nov 2025 C1 malicious — No Details →
1.0.103 27 Nov 2025 C1 malicious — No Details →
1.0.102 27 Nov 2025 C1 malicious — No Details →
1.0.101 27 Nov 2025 C1 malicious — No Details →
1.0.100 26 Nov 2025 C1 malicious — No Details →
1.0.99 26 Nov 2025 C1 malicious — No Details →
1.0.98 26 Nov 2025 C1 malicious — No Details →
1.0.97 26 Nov 2025 C1 malicious — No Details →
1.0.96 26 Nov 2025 C1 malicious — No Details →
1.0.95 25 Nov 2025 C1 malicious — No Details →
1.0.94 24 Nov 2025 C1 malicious — No Details →
1.0.92 18 Nov 2025 C1 malicious — No Details →
1.0.91 13 Nov 2025 C1 malicious — No Details →
1.0.90 12 Nov 2025 C1 malicious — No Details →
1.0.89 12 Nov 2025 C1 malicious — No Details →
1.0.88 05 Nov 2025 C1 malicious — No Details →
1.0.87 04 Nov 2025 C1 malicious — No Details →
1.0.86 21 Oct 2025 C1 malicious — No Details →
1.0.85 19 Oct 2025 C1 malicious — No Details →
1.0.84 17 Oct 2025 C1 malicious — No Details →
1.0.83 17 Oct 2025 C1 malicious — No Details →
1.0.82 16 Oct 2025 C1 malicious — No Details →
1.0.81 15 Oct 2025 C1 malicious — No Details →
1.0.80 10 Oct 2025 C1 malicious — No Details →
1.0.79 08 Oct 2025 C1 malicious — No Details →
1.0.78 06 Oct 2025 C1 malicious — No Details →
1.0.77 01 Oct 2025 C1 malicious — No Details →
1.0.76 29 Sep 2025 C1 malicious — No Details →
1.0.75 25 Sep 2025 C1 malicious — No Details →
1.0.74 23 Sep 2025 C1 malicious — No Details →
1.0.73 19 Sep 2025 C1 malicious — No Details →
1.0.72 19 Sep 2025 C1 malicious — No Details →
1.0.71 19 Sep 2025 C1 malicious — No Details →
1.0.70 19 Sep 2025 C1 malicious — No Details →
1.0.69 18 Sep 2025 C1 malicious — No Details →
1.0.68 18 Sep 2025 C1 malicious — No Details →
1.0.54-main.0 17 Sep 2025 C1 malicious — No Details →
1.0.67 18 Jul 2025 C1 malicious — No Details →
1.0.66 18 Jul 2025 C1 malicious — No Details →
1.0.65 18 Jul 2025 C1 malicious — No Details →
1.0.63 19 May 2025 C1 malicious — No Details →
1.0.62 07 Apr 2025 C1 malicious — No Details →
1.0.61 07 Apr 2025 C1 malicious — No Details →
1.0.60 05 Mar 2025 C1 malicious — No Details →
1.0.59 04 Mar 2025 C1 malicious — No Details →
1.0.58 03 Dec 2024 C1 malicious — No Details →
1.0.57 28 Nov 2024 C1 malicious — No Details →
1.0.56 28 Nov 2024 C1 malicious — No Details →
1.0.55 15 Oct 2024 C1 malicious — No Details →
1.0.54 15 Oct 2024 C1 malicious — No Details →
1.0.53 15 Oct 2024 C1 malicious — No Details →
1.0.52 15 Oct 2024 C1 malicious — No Details →
1.0.51 15 Oct 2024 C1 malicious — No Details →
1.0.50 14 Oct 2024 C1 malicious — No Details →
1.0.49 08 Oct 2024 C1 malicious — No Details →
1.0.48 17 Sep 2024 C1 malicious — No Details →
1.0.47 16 Sep 2024 C1 malicious — No Details →
1.0.46 10 Sep 2024 C1 malicious — No Details →
1.0.45 09 Sep 2024 C1 malicious — No Details →
1.0.44 06 Sep 2024 C1 malicious — No Details →
1.0.43 04 Sep 2024 C1 malicious — No Details →
1.0.42 03 Sep 2024 C1 malicious — No Details →
1.0.41 03 Sep 2024 C1 malicious — No Details →
1.0.40 02 Sep 2024 C1 malicious — No Details →
1.0.39 30 Aug 2024 C1 malicious — No Details →
1.0.38 27 Aug 2024 C1 malicious — No Details →
1.0.37 27 Aug 2024 C1 malicious — No Details →
1.0.36 27 Aug 2024 C1 malicious — No Details →
1.0.35 27 Aug 2024 C1 malicious — No Details →
1.0.34 24 Aug 2024 C1 malicious — No Details →
1.0.33 22 Aug 2024 C1 malicious — No Details →
1.0.32 22 Aug 2024 C1 malicious — No Details →
1.0.31 21 Aug 2024 C1 malicious — No Details →

The newest 120 of 151 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 @dev-blinq/ui-systems

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 @dev-blinq/ui-systems Package N/A critical No fix published 25 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 @dev-blinq/ui-systems

Is @dev-blinq/ui-systems safe to use?

No. Vulert records a malicious-package vulnerability for @dev-blinq/ui-systems: 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 @dev-blinq/ui-systems's Vulert package health score?

Vulert scores @dev-blinq/ui-systems 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 @dev-blinq/ui-systems affected?

Yes. 1.0.151, 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 @dev-blinq/ui-systems should I use?

1.0.151 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 @dev-blinq/ui-systems have?

1 vulnerability is recorded for @dev-blinq/ui-systems 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 @dev-blinq/ui-systems vulnerabilities disclosed?

1 vulnerability was recorded for @dev-blinq/ui-systems in the last 12 months, and the oldest entry in this database dates to 25 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 @dev-blinq/ui-systems 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 @dev-blinq/ui-systems for upcoming vulnerabilities?

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