NetSight

Security Dashboard

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

Reset
524 matching advisories · page 2 of 18Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
critical GHSA-v26x-mc48-fw33 Malicious code in joni-sambalado47-miaww (npm)Malware npm · joni-sambalado47-miaww 2026-09-17 critical GHSA-4vp6-2j89-w6mw Malicious code in joni-sambalado79-ruro (npm)Malware npm · joni-sambalado79-ruro 2026-09-17 critical GHSA-fx7w-5qjw-hgr4 Malicious code in joko-sambalado4-sukiwir (npm)Malware npm · joko-sambalado4-sukiwir 2026-09-17 critical GHSA-cm66-p28q-v2p6 Malicious code in joko-sambalado31-riris (npm)Malware npm · joko-sambalado31-riris 2026-09-17 critical GHSA-qqjv-mf8c-m9xm Malicious code in joko-sambalado71-sukiwir (npm)Malware npm · joko-sambalado71-sukiwir 2026-09-17 critical GHSA-r7f2-9w4v-3j5p Malicious code in joko-sambalado10-wekto (npm)Malware npm · joko-sambalado10-wekto 2026-09-17 critical GHSA-qw2c-vjc7-h9g7 Malicious code in joko-sambalado33-breki (npm)Malware npm · joko-sambalado33-breki 2026-09-17 critical GHSA-rc6r-r73c-5jpq Malicious code in joko-sambalado74-ruro (npm)Malware npm · joko-sambalado74-ruro 2026-09-17 critical GHSA-6hp4-w9hq-wf4x Malicious code in joko-sambalado70-sluey (npm)Malware npm · joko-sambalado70-sluey 2026-09-17 critical GHSA-gjq7-jcr4-6cqv Malicious code in joko-sambalado59-breki (npm)Malware npm · joko-sambalado59-breki 2026-09-17 critical GHSA-gf42-83pg-hg85 Malicious code in jaja-sambalado67-breki (npm)Malware npm · jaja-sambalado67-breki 2026-09-13 critical GHSA-r4g6-xgr5-4g39 Malicious code in jaja-sambalado83-sluey (npm)Malware npm · jaja-sambalado83-sluey 2026-09-13 critical GHSA-4f9c-j2r2-6vh5 Malicious code in jaja-sambalado77-sluey (npm)Malware npm · jaja-sambalado77-sluey 2026-09-13 critical GHSA-c78g-pm4g-3hr9 Malicious code in iwan-sambalado95-breki (npm)Malware npm · iwan-sambalado95-breki 2026-09-13 critical GHSA-vvjj-f8jw-xjp5 Malicious code in iwan-sambalado90-riris (npm)Malware npm · iwan-sambalado90-riris 2026-09-13 critical GHSA-xx72-ggjv-x79v Malicious code in iwan-sambalado36-riris (npm)Malware npm · iwan-sambalado36-riris 2026-09-13 critical GHSA-p3fw-qhjh-w57p Malicious code in irma-sambalado7-sluey (npm)Malware npm · irma-sambalado7-sluey 2026-09-13 critical GHSA-569r-5hvf-69qq Malicious code in irma-sambalado25-breki (npm)Malware npm · irma-sambalado25-breki 2026-09-13 critical GHSA-33mx-jw7m-3r27 Malicious code in indah-sambalado97-miaww (npm)Malware npm · indah-sambalado97-miaww 2026-09-13 critical GHSA-wfm5-cv42-5f32 Malicious code in indah-sambalado42-ruro (npm)Malware npm · indah-sambalado42-ruro 2026-09-13 critical GHSA-rmw7-j2pq-mrp4 Malicious code in indah-sambalado71-riris (npm)Malware npm · indah-sambalado71-riris 2026-09-13 critical GHSA-rg82-p39j-xh4r Malicious code in ida-sambalado6-breki (npm)Malware npm · ida-sambalado6-breki 2026-09-13 critical GHSA-hfx5-rq4h-x6hw Malicious code in ida-sambalado36-breki (npm)Malware npm · ida-sambalado36-breki 2026-09-13 critical GHSA-hp2v-vq95-j4qm Malicious code in ida-sambalado51-riris (npm)Malware npm · ida-sambalado51-riris 2026-09-13 critical GHSA-h5q8-33r3-x5r8 Malicious code in hendra-sambalado27-breki (npm)Malware npm · hendra-sambalado27-breki 2026-09-13 critical GHSA-6p53-cmqh-rfvj Malicious code in hendra-sambalado84-miaww (npm)Malware npm · hendra-sambalado84-miaww 2026-09-13 critical GHSA-95cm-2c5g-3pww Malicious code in hendra-sambalado67-riris (npm)Malware npm · hendra-sambalado67-riris 2026-09-13 critical GHSA-4x8p-p4fx-mpw7 Malicious code in hendra-sambalado60-remi (npm)Malware npm · hendra-sambalado60-remi 2026-09-13 critical GHSA-mx3f-pjc6-g35c Malicious code in hanafi-sambalado13-miaww (npm)Malware npm · hanafi-sambalado13-miaww 2026-09-13 critical GHSA-vprp-5ccg-v5wj Malicious code in hanafi-sambalado70-kyuki (npm)Malware npm · hanafi-sambalado70-kyuki 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.