NetSight

Security Dashboard

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

Reset
509 matching advisories · page 5 of 17Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
critical GHSA-q429-887q-8h2x Malicious code in hitachi-poke45 (npm)Malware npm · hitachi-poke45 2026-09-13 critical GHSA-fp89-frpf-8348 Malicious code in hitachi-poke23 (npm)Malware npm · hitachi-poke23 2026-09-13 critical GHSA-m5gg-p9hw-68c8 Malicious code in hitachi-poke15 (npm)Malware npm · hitachi-poke15 2026-09-13 critical GHSA-q52p-4w2c-92hv Malicious code in hitachi-poke48 (npm)Malware npm · hitachi-poke48 2026-09-13 critical GHSA-8gjf-25wm-82x7 Malicious code in hitachi-poke47 (npm)Malware npm · hitachi-poke47 2026-09-13 critical GHSA-73w7-hrw9-7xv3 Malicious code in hitachi-poke49 (npm)Malware npm · hitachi-poke49 2026-09-13 critical GHSA-v48v-wfj4-hrr7 Malicious code in hitachi-poke3 (npm)Malware npm · hitachi-poke3 2026-09-13 critical GHSA-59jq-58g5-g8f7 Malicious code in hitachi-poke28 (npm)Malware npm · hitachi-poke28 2026-09-13 critical GHSA-4ggh-rqqg-5g87 Malicious code in hitachi-poke25 (npm)Malware npm · hitachi-poke25 2026-09-13 critical GHSA-9jw7-p957-qr74 Malicious code in hitachi-poke29 (npm)Malware npm · hitachi-poke29 2026-09-13 critical GHSA-25rg-74m4-w5xw Malicious code in hitachi-poke123 (npm)Malware npm · hitachi-poke123 2026-09-13 critical GHSA-g6gw-4h2h-rf3m Malicious code in hitachi-poke104 (npm)Malware npm · hitachi-poke104 2026-09-13 critical GHSA-r4m5-wrgx-62fg Malicious code in hitachi-poke114 (npm)Malware npm · hitachi-poke114 2026-09-13 critical GHSA-xx4p-4pp7-h4mw Malicious code in hitachi-poke113 (npm)Malware npm · hitachi-poke113 2026-09-13 critical GHSA-gqx9-6cm8-ch2h Malicious code in hitachi-poke108 (npm)Malware npm · hitachi-poke108 2026-09-13 critical GHSA-565g-ghmq-vxj6 Malicious code in hitachi-poke115 (npm)Malware npm · hitachi-poke115 2026-09-13 critical GHSA-96hm-hf3p-75j3 Malicious code in hitachi-poke118 (npm)Malware npm · hitachi-poke118 2026-09-13 critical GHSA-c7vr-wq28-j5cj Malicious code in hitachi-poke116 (npm)Malware npm · hitachi-poke116 2026-09-13 critical GHSA-r44v-5f96-q33m Malicious code in hitachi-poke110 (npm)Malware npm · hitachi-poke110 2026-09-13 critical GHSA-whrj-886j-6f7x Malicious code in hitachi-poke10 (npm)Malware npm · hitachi-poke10 2026-09-13 critical GHSA-fcjh-8v6g-m7m8 Malicious code in hitachi-poke122 (npm)Malware npm · hitachi-poke122 2026-09-13 critical GHSA-2wrh-mmw7-qg3x Malicious code in hitachi-poke120 (npm)Malware npm · hitachi-poke120 2026-09-13 critical GHSA-j9qp-grc4-8w6r Malicious code in hitachi-poke109 (npm)Malware npm · hitachi-poke109 2026-09-13 critical GHSA-63c9-mm97-hqx6 Malicious code in hitachi-poke11 (npm)Malware npm · hitachi-poke11 2026-09-13 critical GHSA-724v-8hr2-phcp Malicious code in hitachi-poke105 (npm)Malware npm · hitachi-poke105 2026-09-13 critical GHSA-7mq3-f693-qxx2 Malicious code in hitachi-poke103 (npm)Malware npm · hitachi-poke103 2026-09-13 critical GHSA-w5x7-2rfw-cqhw Malicious code in hitachi-poke125 (npm)Malware npm · hitachi-poke125 2026-09-13 critical GHSA-62gx-h4qc-57p4 Malicious code in hitachi-poke112 (npm)Malware npm · hitachi-poke112 2026-09-13 critical GHSA-92r9-4x2w-23q9 Malicious code in hitachi-poke107 (npm)Malware npm · hitachi-poke107 2026-09-13 critical GHSA-hv42-667f-q4qm Malicious code in hitachi-poke111 (npm)Malware npm · hitachi-poke111 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.