NetSight

Security Dashboard

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

Reset
509 matching advisories · page 3 of 17Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
critical GHSA-pqqm-qxxg-xv5q Malicious code in hitachi-poke67 (npm)Malware npm · hitachi-poke67 2026-09-13 critical GHSA-jwqr-pvc9-wrwg Malicious code in hitachi-poke66 (npm)Malware npm · hitachi-poke66 2026-09-13 critical GHSA-67gw-wfpw-6w8f Malicious code in hitachi-poke76 (npm)Malware npm · hitachi-poke76 2026-09-13 critical GHSA-m265-ccqp-5q7h Malicious code in hitachi-poke75 (npm)Malware npm · hitachi-poke75 2026-09-13 critical GHSA-hqmc-86vq-2q93 Malicious code in hitachi-poke79 (npm)Malware npm · hitachi-poke79 2026-09-13 critical GHSA-fqxr-55fx-c4c9 Malicious code in hitachi-poke71 (npm)Malware npm · hitachi-poke71 2026-09-13 critical GHSA-rrfq-mxw3-3xcf Malicious code in hitachi-poke8 (npm)Malware npm · hitachi-poke8 2026-09-13 critical GHSA-q5m5-5m8p-f6qv Malicious code in hitachi-poke62 (npm)Malware npm · hitachi-poke62 2026-09-13 critical GHSA-c7w9-vf89-cvx6 Malicious code in hitachi-poke61 (npm)Malware npm · hitachi-poke61 2026-09-13 critical GHSA-hhp4-cp9x-gg69 Malicious code in hitachi-poke6 (npm)Malware npm · hitachi-poke6 2026-09-13 critical GHSA-hr4h-47g6-qjrg Malicious code in hitachi-poke57 (npm)Malware npm · hitachi-poke57 2026-09-13 critical GHSA-3j45-54gg-cp7j Malicious code in hitachi-poke60 (npm)Malware npm · hitachi-poke60 2026-09-13 critical GHSA-5497-h5rf-cp68 Malicious code in hitachi-poke55 (npm)Malware npm · hitachi-poke55 2026-09-13 critical GHSA-5hcq-xxw4-34q4 Malicious code in hitachi-poke54 (npm)Malware npm · hitachi-poke54 2026-09-13 critical GHSA-7gjg-xwgv-jcjm Malicious code in hitachi-poke52 (npm)Malware npm · hitachi-poke52 2026-09-13 critical GHSA-vcv4-6qh2-3875 Malicious code in hitachi-poke82 (npm)Malware npm · hitachi-poke82 2026-09-13 critical GHSA-mpr8-83g4-4cq2 Malicious code in hitachi-poke78 (npm)Malware npm · hitachi-poke78 2026-09-13 critical GHSA-g7fw-29m2-h622 Malicious code in hitachi-poke77 (npm)Malware npm · hitachi-poke77 2026-09-13 critical GHSA-42q6-49pw-c8vw Malicious code in hitachi-poke7 (npm)Malware npm · hitachi-poke7 2026-09-13 critical GHSA-xfm8-fwrm-w4pq Malicious code in hitachi-poke63 (npm)Malware npm · hitachi-poke63 2026-09-13 critical GHSA-g22r-5c3f-59h2 Malicious code in hitachi-poke65 (npm)Malware npm · hitachi-poke65 2026-09-13 critical GHSA-q9rq-8mcq-g7f2 Malicious code in hitachi-poke53 (npm)Malware npm · hitachi-poke53 2026-09-13 critical GHSA-8r4w-q7q6-v3r5 Malicious code in hitachi-poke43 (npm)Malware npm · hitachi-poke43 2026-09-13 critical GHSA-634f-c25w-8gg3 Malicious code in hitachi-poke35 (npm)Malware npm · hitachi-poke35 2026-09-13 critical GHSA-6pj6-gxp4-925g Malicious code in hitachi-poke33 (npm)Malware npm · hitachi-poke33 2026-09-13 critical GHSA-xm8j-rf8x-p6cm Malicious code in hitachi-poke36 (npm)Malware npm · hitachi-poke36 2026-09-13 critical GHSA-r9xc-vhrm-w957 Malicious code in hitachi-poke20 (npm)Malware npm · hitachi-poke20 2026-09-13 critical GHSA-6vc8-76qc-g8gc Malicious code in hitachi-poke19 (npm)Malware npm · hitachi-poke19 2026-09-13 critical GHSA-wh7x-69c8-fwwh Malicious code in hitachi-poke17 (npm)Malware npm · hitachi-poke17 2026-09-13 critical GHSA-gf8g-2mr5-8gwg Malicious code in hitachi-poke121 (npm)Malware npm · hitachi-poke121 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.