NetSight

Security Dashboard

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

Reset
3,283 matching advisories · page 6 of 110Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
critical GHSA-gqw5-744m-ff5v Malicious code in lima-echo-dibo (npm)Malware npm · lima-echo-dibo 2026-09-17 critical GHSA-5ccf-wf5x-6cg8 Malicious code in lilypad-violet-qoo759-project (npm)Malware npm · lilypad-violet-qoo759-project 2026-09-17 critical GHSA-qf5v-483h-gg68 Malicious code in lilac-gorge-txc607-project (npm)Malware npm · lilac-gorge-txc607-project 2026-09-17 critical GHSA-788q-h8pr-f6f5 Malicious code in lilac-iris-ozy598-project (npm)Malware npm · lilac-iris-ozy598-project 2026-09-17 critical GHSA-rx7x-jwr7-9gfg Malicious code in lilac-willow-jef539-project (npm)Malware npm · lilac-willow-jef539-project 2026-09-17 critical GHSA-73cf-x2j7-3qf5 Malicious code in lilaosyst (npm)Malware npm · lilaosyst 2026-09-17 critical GHSA-ph35-95pp-wf5h Malicious code in likely-teal-cardinal (npm)Malware npm · likely-teal-cardinal 2026-09-17 critical GHSA-jhmx-7f55-gg33 Malicious code in likely-rose-platypus (npm)Malware npm · likely-rose-platypus 2026-09-17 critical GHSA-f5wr-pxq2-9m8h Malicious code in lighthouse-date-hf2i (npm)Malware npm · lighthouse-date-hf2i 2026-09-17 critical GHSA-jf53-6f47-49m7 Malicious code in light_dingo_z3n (npm)Malware npm · light_dingo_z3n 2026-09-17 critical GHSA-8mr3-3wf5-w842 Malicious code in library-ganymede-axios-phoebe (npm)Malware npm · library-ganymede-axios-phoebe 2026-09-17 critical GHSA-g753-39f5-x25c Malicious code in libbsd (npm)Malware npm · libbsd 2026-09-17 critical GHSA-rf5q-9fw3-7fg8 Malicious code in liambutler (npm)Malware npm · liambutler 2026-09-17 critical GHSA-rp98-vf55-c24r Malicious code in liamdavies (npm)Malware npm · liamdavies 2026-09-17 critical GHSA-7rfm-vx37-96f5 Malicious code in lia-32 (npm)Malware npm · lia-32 2026-09-17 critical GHSA-hxm7-rmpj-fhf5 Malicious code in levels-yaml-build-shelljs (npm)Malware npm · levels-yaml-build-shelljs 2026-09-17 critical GHSA-fhxr-f5px-5vv5 Malicious code in leo-password-reset-service (npm)Malware npm · leo-password-reset-service 2026-09-17 critical GHSA-2qvv-9j45-f5vq Malicious code in lemon-yankee-tjcb (npm)Malware npm · lemon-yankee-tjcb 2026-09-17 critical GHSA-f5jv-vwf2-mxjf Malicious code in lemon-foxtrot-kiwi-kcomt (npm)Malware npm · lemon-foxtrot-kiwi-kcomt 2026-09-17 critical GHSA-c6q4-rpf5-8mvg Malicious code in legal_sole_z3n (npm)Malware npm · legal_sole_z3n 2026-09-17 critical GHSA-f5cv-9vqr-x6v3 Malicious code in legal_whitefish_requirement (npm)Malware npm · legal_whitefish_requirement 2026-09-17 critical GHSA-f582-vf3w-xrpp Malicious code in ledlamp (npm)Malware npm · ledlamp 2026-09-17 critical GHSA-cqc9-f5fp-r45q Malware in randompkgdMalware npm · randompkgd 2026-09-17 critical GHSA-g5mj-84gx-f5jw Malicious code in leadconduit-towerdata (npm)Malware npm · leadconduit-towerdata 2026-09-17 critical GHSA-f542-gj6g-vh2w Malicious code in ldoash (npm)Malware npm · ldoash 2026-09-17 critical GHSA-f5m7-249q-8phj Malicious code in lc50uo (npm)Malware npm · lc50uo 2026-09-17 critical GHSA-wwrw-gh49-vwf5 Malicious code in layla-poke89 (npm)Malware npm · layla-poke89 2026-09-17 critical GHSA-p4gj-88f5-m62c Malicious code in layla-poke57 (npm)Malware npm · layla-poke57 2026-09-17 critical GHSA-qvf5-cvpq-8xcj Malicious code in lasertank (npm)Malware npm · lasertank 2026-09-17 critical GHSA-wmpf-4p8q-f5f2 Malicious code in laredoute (npm)Malware npm · laredoute 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.