NetSight

Security Dashboard

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

Reset
88 matching advisories · page 3 of 3Index is being built · Subscribe · RSS
SeverityIDTitleAffectedAge
critical GHSA-j28w-m3pf-28ph Malicious code in combined-yellow-dingo (npm)Malware npm · combined-yellow-dingo 2026-09-04 critical GHSA-6mmv-8j43-vx2h Malicious code in cold-yellow-crab (npm)Malware npm · cold-yellow-crab 2026-09-04 critical GHSA-r9v3-mpqc-6rrw Malicious code in cloudy-yellow-harrier (npm)Malware npm · cloudy-yellow-harrier 2026-09-04 critical GHSA-38px-xqg6-r5gf Malicious code in clinical-yellow-pig (npm)Malware npm · clinical-yellow-pig 2026-09-04 critical GHSA-gwvv-w6xm-cwwp Malicious code in circular-yellow-marmot (npm)Malware npm · circular-yellow-marmot 2026-09-04 critical GHSA-vhvc-cwgp-7hw9 Malicious code in cherry-yellow-zvf108-project (npm)Malware npm · cherry-yellow-zvf108-project 2026-09-04 critical GHSA-fg82-393g-4vmc Malicious code in chemical-yellow-gazelle (npm)Malware npm · chemical-yellow-gazelle 2026-09-04 critical GHSA-qxjg-g24j-jww4 Malicious code in characteristic-yellow-cardinal (npm)Malware npm · characteristic-yellow-cardinal 2026-09-04 critical GHSA-j8rj-3pq8-xjq9 Malicious code in capitalist-yellow-perch (npm)Malware npm · capitalist-yellow-perch 2026-09-04 critical GHSA-vhq3-xfgm-635w Malicious code in awake-yellow-kingfisher (npm)Malware npm · awake-yellow-kingfisher 2026-09-02 critical GHSA-rrpv-ff5q-h84m Malicious code in ashamed-yellow-butterfly (npm)Malware npm · ashamed-yellow-butterfly 2026-09-02 critical GHSA-rqhp-3jv2-6j2g Malicious code in arrogant-yellow-kangaroo (npm)Malware npm · arrogant-yellow-kangaroo 2026-09-02 critical GHSA-w5x5-gxg5-vp94 Malicious code in arrogant-yellow-bug (npm)Malware npm · arrogant-yellow-bug 2026-09-02 critical GHSA-xwjp-rmc6-h73q Malicious code in ant-yellow-yjs130-project (npm)Malware npm · ant-yellow-yjs130-project 2026-09-02 critical GHSA-gcxv-g744-mjvx Malicious code in annual_jay_yellow-85 (npm)Malware npm · annual_jay_yellow-85 2026-09-02 critical GHSA-mcfr-9689-xrxc Malicious code in agreeable_pony_yellow-15 (npm)Malware npm · agreeable_pony_yellow-15 2026-08-31 critical GHSA-c273-cxcp-72g4 Malicious code in administrative-yellow-yak (npm)Malware npm · administrative-yellow-yak 2026-08-31 critical GHSA-f3rh-872f-9vp5 Malicious code in adequate-yellow-chinchilla (npm)Malware npm · adequate-yellow-chinchilla 2026-08-31 critical GHSA-4mhf-vc39-9f4q Malicious code in added-yellow-tiglon (npm)Malware npm · added-yellow-tiglon 2026-08-31 critical GHSA-hvf6-cp3p-j28f Malicious code in yellorq (PyPI)Malware pip · yellorq 2026-07-21 critical GHSA-w3w4-49m4-5gr3 Malicious code in yellyproxies (PyPI)Malware pip · yellyproxies 2026-07-21 critical GHSA-87w3-vjjr-47gf Malware in yellowdiscordlookupMalware npm · yellowdiscordlookup 2025-12-30 critical GHSA-h8cx-c2ww-pqxx Malware in yellow-pluginsMalware npm · yellow-plugins 2025-05-27 critical GHSA-64hr-5cmh-c2gx Malware in mp3-file-zip-d-ownload-7517-goodbye-yellow-brick-road-h63vl-tpdnhxMalware npm · mp3-file-zip-d-ownload-7517-goodbye-yellow-brick-road-h63vl-tpdnhx 2024-10-16 critical9.8 CVE-2023-0750 Yellobrik PEC-1864 implements authentication checks via javascript in the frontend interface. lynx-technik · yellobrik_pec_1864_firmware 2023-04-06 critical GHSA-4rvw-2pjj-wcqq Malware in yellowbrainMalware npm · yellowbrain 2023-02-06 critical9.0 CVE-2020-19586 Incorrect Access Control issue in Yellowfin Business Intelligence 7.3 allows remote attackers to escalate privilege via MIAdminStyles.i4 Admin UI. yellowfinbi · business_intelligence 2022-09-14 critical GHSA-xv3m-jcfm-4m4v Malware in yello133Malware npm · yello133 2022-06-20

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.