NetSight

Security Dashboard

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

Reset
3,283 matching advisories · page 8 of 110Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
critical GHSA-29g2-j2pf-f5q6 Malicious code in kurniawan-pisang1-riris (npm)Malware npm · kurniawan-pisang1-riris 2026-09-17 critical GHSA-vqf5-vffp-wpx5 Malicious code in kurniawan-peyek46-miaww (npm)Malware npm · kurniawan-peyek46-miaww 2026-09-17 critical GHSA-c3wf-pp3w-pf5w Malicious code in kurniawan-peyek1-riris (npm)Malware npm · kurniawan-peyek1-riris 2026-09-17 critical GHSA-f59r-58cw-49vc Malicious code in kurniawan-moci91-riris (npm)Malware npm · kurniawan-moci91-riris 2026-09-17 critical GHSA-mr7v-f5hm-mcg3 Malicious code in kurniawan-mendoan93-sukiwir (npm)Malware npm · kurniawan-mendoan93-sukiwir 2026-09-17 critical GHSA-3gcr-g3f5-6mww Malicious code in kurniawan-mendut10-breki (npm)Malware npm · kurniawan-mendut10-breki 2026-09-17 critical GHSA-f54m-hrph-8v65 Malicious code in kurniawan-lapis94-miaww (npm)Malware npm · kurniawan-lapis94-miaww 2026-09-17 critical GHSA-2qc2-2gp3-6xf5 Malicious code in kurniawan-gepuk59-sluey (npm)Malware npm · kurniawan-gepuk59-sluey 2026-09-17 critical GHSA-2p8w-3qjq-4pf5 Malicious code in kurniawan-enting35-riris (npm)Malware npm · kurniawan-enting35-riris 2026-09-17 critical GHSA-5393-f5fh-66j5 Malicious code in kurnia-wajit49-sukiwir (npm)Malware npm · kurnia-wajit49-sukiwir 2026-09-17 critical GHSA-834v-3xjq-xpf5 Malicious code in kurnia-tempe13-sukiwir (npm)Malware npm · kurnia-tempe13-sukiwir 2026-09-17 critical GHSA-pgpm-3q42-2f56 Malicious code in kurnia-telur73-sluey (npm)Malware npm · kurnia-telur73-sluey 2026-09-17 critical GHSA-5q2w-f5w2-7jpj Malicious code in kurnia-sroto44-sluey (npm)Malware npm · kurnia-sroto44-sluey 2026-09-17 critical GHSA-f5xq-j3q9-jvxg Malicious code in kurnia-sambel85-riris (npm)Malware npm · kurnia-sambel85-riris 2026-09-17 critical GHSA-jgf3-pxr6-ff5w Malicious code in kurnia-peyek84-sukiwir (npm)Malware npm · kurnia-peyek84-sukiwir 2026-09-17 critical GHSA-646m-rrh2-c2f5 Malicious code in kurnia-rawon4-ruro (npm)Malware npm · kurnia-rawon4-ruro 2026-09-17 critical GHSA-6jf5-p2jh-58jr Malicious code in kurnia-nasipecel85-breki (npm)Malware npm · kurnia-nasipecel85-breki 2026-09-17 critical GHSA-5gxr-qjxc-vwf5 Malicious code in kurnia-miebogor16-ruro (npm)Malware npm · kurnia-miebogor16-ruro 2026-09-17 critical GHSA-49hc-682m-hwf5 Malicious code in kurnia-mieaceh3-miaww (npm)Malware npm · kurnia-mieaceh3-miaww 2026-09-17 critical GHSA-g97w-3r46-f5rf Malicious code in kurnia-moci65-breki (npm)Malware npm · kurnia-moci65-breki 2026-09-17 critical GHSA-36r7-fw64-f5fp Malicious code in kurnia-martabak6-riris (npm)Malware npm · kurnia-martabak6-riris 2026-09-17 critical GHSA-m35x-4cw7-f5g7 Malicious code in kurnia-kue73-wekto (npm)Malware npm · kurnia-kue73-wekto 2026-09-17 critical GHSA-4qh3-fhf5-p76v Malicious code in kurnia-kupat31-miaww (npm)Malware npm · kurnia-kupat31-miaww 2026-09-17 critical GHSA-68vr-prv8-f53c Malicious code in kurnia-lapis93-miaww (npm)Malware npm · kurnia-lapis93-miaww 2026-09-17 critical GHSA-7823-5f5x-c8gx Malicious code in kurnia-buburayam28-ruro (npm)Malware npm · kurnia-buburayam28-ruro 2026-09-17 critical GHSA-m6f5-m98m-pffw Malicious code in kupaio-kulaka-jokioasikimalo (npm)Malware npm · kupaio-kulaka-jokioasikimalo 2026-09-17 critical GHSA-5px3-rff5-34xp Malicious code in kupai-ukuta-jokakai (npm)Malware npm · kupai-ukuta-jokakai 2026-09-17 critical GHSA-7mf5-8mv3-p6r5 Malicious code in kupaio-kila-jakaiaai (npm)Malware npm · kupaio-kila-jakaiaai 2026-09-17 critical GHSA-8c5g-6qj5-f56m Malicious code in kupai-lulikon-igugfu (npm)Malware npm · kupai-lulikon-igugfu 2026-09-17 critical GHSA-f5jj-f755-hr37 Malicious code in kujibiki (npm)Malware npm · kujibiki 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.