NetSight

Security Dashboard

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

Reset
509 matching advisories · page 4 of 17Index updated 9 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
critical GHSA-44qh-4h9h-wpf3 Malicious code in hitachi-poke30 (npm)Malware npm · hitachi-poke30 2026-09-13 critical GHSA-2w2h-vr62-8gcg Malicious code in hitachi-poke26 (npm)Malware npm · hitachi-poke26 2026-09-13 critical GHSA-5p4g-6vxx-q3m3 Malicious code in hitachi-poke46 (npm)Malware npm · hitachi-poke46 2026-09-13 critical GHSA-3qcj-mj28-v27w Malicious code in hitachi-poke39 (npm)Malware npm · hitachi-poke39 2026-09-13 critical GHSA-w2wm-j7hp-3jgg Malicious code in hitachi-poke44 (npm)Malware npm · hitachi-poke44 2026-09-13 critical GHSA-77jm-9vqw-rppq Malicious code in hitachi-poke40 (npm)Malware npm · hitachi-poke40 2026-09-13 critical GHSA-2q58-vrr9-wp59 Malicious code in hitachi-poke42 (npm)Malware npm · hitachi-poke42 2026-09-13 critical GHSA-w3w3-w6jx-35v8 Malicious code in hitachi-poke38 (npm)Malware npm · hitachi-poke38 2026-09-13 critical GHSA-ffg3-hj9m-fcr9 Malicious code in hitachi-poke22 (npm)Malware npm · hitachi-poke22 2026-09-13 critical GHSA-86p3-gjc5-qh9r Malicious code in hitachi-poke24 (npm)Malware npm · hitachi-poke24 2026-09-13 critical GHSA-g26r-3mpm-wxqh Malicious code in hitachi-poke18 (npm)Malware npm · hitachi-poke18 2026-09-13 critical GHSA-95fr-4x6v-5pm3 Malicious code in hitachi-poke16 (npm)Malware npm · hitachi-poke16 2026-09-13 critical GHSA-9qfj-p9f2-4rf7 Malicious code in hitachi-poke130 (npm)Malware npm · hitachi-poke130 2026-09-13 critical GHSA-4wrr-phw6-mcpx Malicious code in hitachi-poke126 (npm)Malware npm · hitachi-poke126 2026-09-13 critical GHSA-8xrq-54xf-r4xg Malicious code in hitachi-poke124 (npm)Malware npm · hitachi-poke124 2026-09-13 critical GHSA-c72f-69m8-8wch Malicious code in hitachi-poke37 (npm)Malware npm · hitachi-poke37 2026-09-13 critical GHSA-xch8-jwpc-2289 Malicious code in hitachi-poke41 (npm)Malware npm · hitachi-poke41 2026-09-13 critical GHSA-jm8j-27hp-6wfp Malicious code in hitachi-poke34 (npm)Malware npm · hitachi-poke34 2026-09-13 critical GHSA-6388-6whm-jmvf Malicious code in hitachi-poke4 (npm)Malware npm · hitachi-poke4 2026-09-13 critical GHSA-9x8m-8463-xvfm Malicious code in hitachi-poke128 (npm)Malware npm · hitachi-poke128 2026-09-13 critical GHSA-c752-q5x6-66gq Malicious code in hitachi-poke129 (npm)Malware npm · hitachi-poke129 2026-09-13 critical GHSA-4544-7c5h-r6x7 Malicious code in hitachi-poke127 (npm)Malware npm · hitachi-poke127 2026-09-13 critical GHSA-q848-8pxv-c2qh Malicious code in hitachi-poke13 (npm)Malware npm · hitachi-poke13 2026-09-13 critical GHSA-q5c2-w75r-v28h Malicious code in hitachi-poke5 (npm)Malware npm · hitachi-poke5 2026-09-13 critical GHSA-2cpf-5p54-wcq3 Malicious code in hitachi-poke32 (npm)Malware npm · hitachi-poke32 2026-09-13 critical GHSA-fc3p-78f7-rvm2 Malicious code in hitachi-poke14 (npm)Malware npm · hitachi-poke14 2026-09-13 critical GHSA-f4x2-gxcg-pxpr Malicious code in hitachi-poke31 (npm)Malware npm · hitachi-poke31 2026-09-13 critical GHSA-m869-85vr-pc2x Malicious code in hitachi-poke27 (npm)Malware npm · hitachi-poke27 2026-09-13 critical GHSA-84ch-xmv6-4h2x Malicious code in hitachi-poke21 (npm)Malware npm · hitachi-poke21 2026-09-13 critical GHSA-w28g-phg9-7qg8 Malicious code in hitachi-poke2 (npm)Malware npm · hitachi-poke2 2026-09-13

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.