NetSight

Security Dashboard

A live picture of new vulnerabilities, flaws exploited in the wild and malicious packages.

Reset
968 matching advisories · page 3 of 33Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
critical GHSA-29m3-r634-c93f Malicious code in laminebaguette (npm)Malware npm · laminebaguette 2026-09-17 critical GHSA-4c23-69hj-cmg9 Malicious code in laminequiche (npm)Malware npm · laminequiche 2026-09-17 critical GHSA-w246-9c6w-gpf3 Malicious code in kuinsu-uki-vilakunnami (npm)Malware npm · kuinsu-uki-vilakunnami 2026-09-17 critical GHSA-rc46-p7p9-gpm2 Malicious code in kuinsu-luuki-vilakunanami (npm)Malware npm · kuinsu-luuki-vilakunanami 2026-09-17 critical GHSA-qcq3-j36m-37r7 Malicious code in kuinsu-uki-vilauami (npm)Malware npm · kuinsu-uki-vilauami 2026-09-17 critical GHSA-fw2j-m8x7-qhvp Malicious code in kuinsu-uuki-vilakunanami (npm)Malware npm · kuinsu-uuki-vilakunanami 2026-09-17 critical GHSA-46f7-5v6p-x7q9 Malicious code in kuinsu-uki-vilami (npm)Malware npm · kuinsu-uki-vilami 2026-09-17 critical GHSA-wjcr-j33f-hh6h Malicious code in kuinsu-lubuki-viunanami (npm)Malware npm · kuinsu-lubuki-viunanami 2026-09-17 critical GHSA-2mw4-mwx3-3w5x Malicious code in kuinsu-lubki-nasiunami (npm)Malware npm · kuinsu-lubki-nasiunami 2026-09-17 critical GHSA-49g8-8j32-pwfq Malicious code in kuinsu-lubuki-nasivnami (npm)Malware npm · kuinsu-lubuki-nasivnami 2026-09-17 critical GHSA-7hqw-797c-5hvh Malicious code in kuinsu-lubuki-vilakunanami (npm)Malware npm · kuinsu-lubuki-vilakunanami 2026-09-17 critical GHSA-xg2m-fchx-grfx Malicious code in kuinsu-lubuki-navnami (npm)Malware npm · kuinsu-lubuki-navnami 2026-09-17 critical GHSA-pp2m-722w-qvcc Malicious code in kuinsu-lubuki-vinami (npm)Malware npm · kuinsu-lubuki-vinami 2026-09-17 critical GHSA-vj52-7q23-hh6w Malicious code in kuinsu-lubuki-nvnami (npm)Malware npm · kuinsu-lubuki-nvnami 2026-09-17 critical GHSA-qvr3-634p-jxqv Malicious code in kuinsu-lubki-nasiami (npm)Malware npm · kuinsu-lubki-nasiami 2026-09-17 critical GHSA-2x73-w8c9-294p Malicious code in kuinsu-lubki-nasinami (npm)Malware npm · kuinsu-lubki-nasinami 2026-09-17 critical GHSA-6x7q-pf2p-r877 Malicious code in kuinsu-lubuki-vianami (npm)Malware npm · kuinsu-lubuki-vianami 2026-09-17 critical GHSA-h8h6-crgf-5j38 Malicious code in kuinsu-lubuki-viakunanami (npm)Malware npm · kuinsu-lubuki-viakunanami 2026-09-17 critical GHSA-66w9-wvgq-5fhm Malicious code in kuinsu-lubuki-nasivanami (npm)Malware npm · kuinsu-lubuki-nasivanami 2026-09-17 critical GHSA-8frr-hxc8-x4mh Malicious code in kuinsu-lubuki-nasiuvanami (npm)Malware npm · kuinsu-lubuki-nasiuvanami 2026-09-17 critical GHSA-px3f-jrwq-7399 Malicious code in kuinsu-lubki-nasiuvanami (npm)Malware npm · kuinsu-lubki-nasiuvanami 2026-09-17 critical GHSA-2r7x-77f2-q2m9 Malicious code in kuinsu-lubuki-vinanami (npm)Malware npm · kuinsu-lubuki-vinanami 2026-09-17 critical GHSA-7x9c-f5jw-jf4h Malicious code in kuinsu-lubki-nasiuvnami (npm)Malware npm · kuinsu-lubki-nasiuvnami 2026-09-17 critical GHSA-whcx-x7g8-7g5p Malicious code in kisut-faig-dikanami (npm)Malware npm · kisut-faig-dikanami 2026-09-17 critical GHSA-9qxw-7jq2-mrqp Malicious code in kisut-fig-dikanamufami (npm)Malware npm · kisut-fig-dikanamufami 2026-09-17 critical GHSA-p3qf-mrj9-9vhw Malicious code in kisut-fafunig-amfacamicufia (npm)Malware npm · kisut-fafunig-amfacamicufia 2026-09-17 critical GHSA-9v7p-37rj-2w3q Malicious code in kisut-diug-danugamicffoa (npm)Malware npm · kisut-diug-danugamicffoa 2026-09-17 critical GHSA-x86h-crm8-5wcq Malicious code in kisut-diug-danamifoa (npm)Malware npm · kisut-diug-danamifoa 2026-09-17 critical GHSA-c7m7-7g6f-653p Malicious code in kisut-fafunig-amfaaicamicufia (npm)Malware npm · kisut-fafunig-amfaaicamicufia 2026-09-17 critical GHSA-m3f5-fjjf-38wj Malicious code in kisut-diug-danugamicfoa (npm)Malware npm · kisut-diug-danugamicfoa 2026-09-17

Get notifications

Subscribe to new vulnerabilities and early warnings from the last seven days. Pick what matters to your stack and copy the address into any feed reader. More filters appear when you pick a type.

Format:
Open feed

Early warnings are advisories that are published before or without a CVE number, for example malicious packages, advisories with a CVE still pending and reports that are not reviewed yet. Confidence says how well an entry is checked: high, medium or low.

About this dashboard

The dashboard keeps its own index of security advisories and refreshes it every 30 minutes. It merges the national vulnerability database, package advisories, malware reports and the catalog of vulnerabilities that are exploited in the wild into one record per issue. Reports about the same flaw are combined, so nothing is listed twice.

Open any entry for the full record: description, severity vector, affected packages and versions, fixed versions, weakness class, exploitation probability and references.

Sources: the GitHub Advisory Database (reviewed advisories, malware reports and unreviewed reports), the National Vulnerability Database, the CVE Program (cve.org) for brand-new records, the OpenSSF malicious packages list, the CISA catalog of Known Exploited Vulnerabilities and Microsoft's blocklist of malicious VS Code extensions. Every entry names its sources on its detail page.

This product uses the NVD API but is not endorsed or certified by the NVD.

Reading the figures

  • Threat level: a rating computed from three numbers shown next to it: critical advisories in the last 24 hours, vulnerabilities newly confirmed as exploited this week and malware reports this week. It is a quick orientation, not an official warning level.
  • Severity: scores from 9.0 are critical, 7.0 to 8.9 high, 4.0 to 6.9 medium and 0.1 to 3.9 low. Severity describes how bad a flaw is in general. It does not know whether the component is reachable in your environment.
  • Known exploited: exploitation has been observed in real attacks. These are the entries to patch first. Entries with a fix deadline show how many days are left.
  • Early warnings: advisories that appear before or without a CVE number, for example malicious packages, reviewed advisories with a CVE still pending and reports that are not reviewed yet.
  • Priority queue: critical and high advisories of the last 7 days and everything newly exploited, ordered by exploitation status, severity and score.

Questions

Where does the data come from?
From public vulnerability databases, package advisories and the catalog of exploited vulnerabilities. NetSight collects them into its own index every 30 minutes and merges duplicates.
How do I check whether I am affected?
Search for your product or package name, open the record and compare your installed version with the affected and fixed versions. A product name alone does not mean your version is affected.
What does known exploited mean?
Exploitation of this vulnerability has been observed in real attacks. Such entries carry a date they were confirmed and, where one exists, a deadline for applying the fix.
What is an early warning?
An advisory that is published before or without a CVE number, such as a malicious package or a reviewed advisory whose CVE is still pending. They give you a head start, but the details can change.
Is a high severity always more urgent than a low one?
No. Severity measures technical impact in general. Exposure of the affected system, observed exploitation and the exploitation probability matter as much.
Can I follow new advisories automatically?
Yes. Use the notification builder further down to create an RSS, Atom or JSON feed filtered by severity, technology, ecosystem or exploitation status.