NetSight

Security Dashboard

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

Reset
235 matching advisories · page 4 of 8Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
critical GHSA-m3x3-w9p3-wfc7 Malicious code in @zalastax/nolb-autt (npm)Malware npm · @zalastax/nolb-autt 2026-08-14 critical GHSA-gx3q-hwq5-v832 Malicious code in dolyame-ui-inputtag (npm)Malware npm · dolyame-ui-inputtag 2026-08-07 critical GHSA-8x86-rh4c-m9xf Malicious code in dolyame-ui-inputtools (npm)Malware npm · dolyame-ui-inputtools 2026-08-07 critical GHSA-v55h-m4jc-mhgh Malicious code in dolyame-ui-inputtime (npm)Malware npm · dolyame-ui-inputtime 2026-08-07 critical GHSA-p5qq-7xpw-7qrx Malicious code in dolyame-ui-buttonstore (npm)Malware npm · dolyame-ui-buttonstore 2026-08-07 critical GHSA-6r9r-p7ch-x848 Malware in bnpl-blocks-atom-bnpl-dolyame-buttonMalware npm · bnpl-blocks-atom-bnpl-dolyame-button 2026-08-05 critical GHSA-f3r5-jmpg-pmrm Malware in dolyame-boxy-independent-bnpl-buttonMalware npm · dolyame-boxy-independent-bnpl-button 2026-08-05 critical GHSA-gxfp-gfm5-6f92 Malware in bnpl-blocks-atom-bnpl-buttonMalware npm · bnpl-blocks-atom-bnpl-button 2026-08-05 critical GHSA-hf9m-4wxq-3fcq Malware in dolyame-boxy-desktop-bnpl-button-setMalware npm · dolyame-boxy-desktop-bnpl-button-set 2026-08-05 critical GHSA-p8jq-ggcc-9fvg Malware in dolyame-boxy-atom-bnpl-dolyame-buttonMalware npm · dolyame-boxy-atom-bnpl-dolyame-button 2026-08-05 critical GHSA-6qhp-2g9g-gg7g Malicious code in dolyame-boxy-mobile-bnpl-button-set (npm)Malware npm · dolyame-boxy-mobile-bnpl-button-set 2026-08-05 critical GHSA-j6hc-mqrc-9px4 Malicious code in dolyame-boxy-independent-bnpl-button (npm)Malware npm · dolyame-boxy-independent-bnpl-button 2026-08-05 critical GHSA-qv85-5xrh-2x43 Malicious code in dolyame-boxy-atom-bnpl-dolyame-button (npm)Malware npm · dolyame-boxy-atom-bnpl-dolyame-button 2026-08-05 critical GHSA-crr3-jgr3-wrcj Malicious code in dolyame-boxy-atom-bnpl-button (npm)Malware npm · dolyame-boxy-atom-bnpl-button 2026-08-05 critical GHSA-4mfv-j34j-xx9j Malicious code in dolyame-boxy-atom-bnpl-store-button-set (npm)Malware npm · dolyame-boxy-atom-bnpl-store-button-set 2026-08-05 critical GHSA-hv2w-q8f8-f58p Malicious code in dolyame-boxy-desktop-bnpl-button-set (npm)Malware npm · dolyame-boxy-desktop-bnpl-button-set 2026-08-05 critical GHSA-xp3x-7m7p-57w6 Malware in dolyame-boxy-atom-bnpl-buttonMalware npm · dolyame-boxy-atom-bnpl-button 2026-08-05 critical GHSA-4f3v-vg7g-x67h Malware in @nebula.js/sn-action-buttonMalware npm · @nebula.js/sn-action-button 2026-08-04 critical GHSA-ffmh-34qf-89jg Malware in @onereach/si-a-buttonMalware npm · @onereach/si-a-button, npm · @onereach/si-a-button, npm · @onereach/si-a-button 2026-08-04 critical GHSA-6vfm-x5rq-5gqr Malware in chalk-buttonMalware npm · chalk-button 2026-07-30 critical GHSA-rp59-qq3q-276w Malware in chalk-buttonsMalware npm · chalk-buttons 2026-07-30 critical GHSA-rc5f-67q5-hfv2 Malicious code in personal-custom-button (npm)Malware npm · personal-custom-button, npm · personal-custom-button, npm · personal-custom-button +5 2026-07-27 critical GHSA-hm67-m69v-pw55 Malicious code in @gutierre0x80/ads.components.button (npm)Malware npm · @gutierre0x80/ads.components.button 2026-07-27 critical GHSA-hcxj-25f6-9jp5 Malicious code in shoots-flutter (PyPI)Malware pip · shoots-flutter 2026-07-21 critical GHSA-wxcm-836g-m72g Malicious code in puttytitle (PyPI)Malware pip · puttytitle 2026-07-21 critical GHSA-qvwq-pchw-58g3 Malicious code in psuttil (PyPI)Malware pip · psuttil 2026-07-21 critical GHSA-g43j-cgg9-q32p Malicious code in blabutt (PyPI)Malware pip · blabutt 2026-07-21 critical GHSA-5926-wm74-qhc9 Malicious code in bip-uttils (PyPI)Malware pip · bip-uttils 2026-07-21 critical GHSA-f2gf-fm5r-6jr6 Malicious code in beauttifulsoup4 (PyPI)Malware pip · beauttifulsoup4 2026-07-21 critical GHSA-63gv-c5hr-2cr2 Malicious code in beauttifulsoup (PyPI)Malware pip · beauttifulsoup 2026-07-21

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.