NetSight

Security Dashboard

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

Reset
268 matching advisories · page 4 of 9Index updated 8 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
critical GHSA-4xpc-mmv7-wj58 Malicious code in carpo-centauri-commitlint-config-angular-callback (npm)Malware npm · carpo-centauri-commitlint-config-angular-callback 2026-09-04 critical GHSA-mhmm-ph8j-939r Malicious code in capes-template-angular (npm)Malware npm · capes-template-angular, npm · capes-template-angular, npm · capes-template-angular +1 2026-09-04 critical GHSA-vr6g-7hpc-7wv4 Malicious code in barnard-html-webpack-plugin-commitlint-config-angular-prettier (npm)Malware npm · barnard-html-webpack-plugin-commitlint-config-angular-prettier 2026-09-02 critical GHSA-278c-qx33-8prw Malicious code in barnard-css-minimizer-webpack-plugin-dependencies-commitlint-config-angular (npm)Malware npm · barnard-css-minimizer-webpack-plugin-dependencies-commitlint-config-angular 2026-09-02 critical GHSA-8gc3-vcjq-r4fg Malicious code in barco-angular-ui-bootstrap (npm)Malware npm · barco-angular-ui-bootstrap 2026-09-02 critical GHSA-vq2r-jr3v-86r5 Malicious code in bangscripts-angular (npm)Malware npm · bangscripts-angular 2026-09-02 critical GHSA-j42q-364g-8f69 Malicious code in aws-billing-console-angular (npm)Malware npm · aws-billing-console-angular 2026-09-02 critical GHSA-w42f-3cj5-mwg7 Malicious code in avior-commitlint-config-angular-cypress-quark (npm)Malware npm · avior-commitlint-config-angular-cypress-quark 2026-09-02 critical GHSA-2x74-vg5m-rfw8 Malicious code in astrophysics-commitlint-config-angular-unuk-luna (npm)Malware npm · astrophysics-commitlint-config-angular-unuk-luna 2026-09-02 critical GHSA-gwf7-273h-v4cm Malicious code in ashok-angular2-login (npm)Malware npm · ashok-angular2-login 2026-09-02 critical GHSA-9x63-g3m9-rxhx Malicious code in ariel-spawn-commitlint-config-angular-cressida (npm)Malware npm · ariel-spawn-commitlint-config-angular-cressida 2026-09-02 critical GHSA-47vr-fw72-ffjr Malicious code in ariel-callisto-commitlint-config-angular-install (npm)Malware npm · ariel-callisto-commitlint-config-angular-install 2026-09-02 critical GHSA-9f2r-h8qj-4vxf Malicious code in aou-ui-angular (npm)Malware npm · aou-ui-angular 2026-09-02 critical GHSA-58q8-wjqq-r4rv Malicious code in antimatter-commitlint-config-angular-archaeoastronomy-lint (npm)Malware npm · antimatter-commitlint-config-angular-archaeoastronomy-lint 2026-09-02 critical GHSA-pr2f-c74c-q688 Malicious code in angular2-security (npm)Malware npm · angular2-security 2026-09-02 critical GHSA-vc69-x46w-gh8r Malicious code in angular-portal-azure (npm)Malware npm · angular-portal-azure 2026-09-02 critical GHSA-6v2c-xpxp-gmpj Malicious code in angulargp (npm)Malware npm · angulargp 2026-09-02 critical GHSA-j22w-xqjr-jpc5 Malicious code in angular-webpart (npm)Malware npm · angular-webpart 2026-09-02 critical GHSA-769g-7cgw-6jg3 Malicious code in angular-promql (npm)Malware npm · angular-promql 2026-09-02 critical GHSA-758g-g6h8-7xxm Malicious code in angular-leveled-reader (npm)Malware npm · angular-leveled-reader 2026-09-02 critical GHSA-6xf7-g9cr-mp4w Malicious code in angular-mep (npm)Malware npm · angular-mep 2026-09-02 critical GHSA-3hr6-g4w6-fgcw Malicious code in angular2-safe-provider (npm)Malware npm · angular2-safe-provider 2026-09-02 critical GHSA-9365-c2x2-6mrv Malicious code in angular-hw-cache (npm)Malware npm · angular-hw-cache 2026-09-02 critical GHSA-f79j-q847-928x Malicious code in angular-sources (npm)Malware npm · angular-sources 2026-09-02 critical GHSA-x3x9-fmv4-hjr8 Malicious code in angular2-tesla-common-1 (npm)Malware npm · angular2-tesla-common-1, npm · angular2-tesla-common-1 2026-09-02 critical GHSA-ffwx-rvr6-r8qq Malicious code in angularjs-in-view (npm)Malware npm · angularjs-in-view 2026-09-02 critical GHSA-g838-cwpm-xc42 Malicious code in angular-rs-alerts (npm)Malware npm · angular-rs-alerts 2026-09-02 critical GHSA-pr46-pj9q-hvjf Malicious code in angular-truncate (npm)Malware npm · angular-truncate 2026-09-02 critical GHSA-fp6j-2pvh-f534 Malicious code in angular-tileview (npm)Malware npm · angular-tileview 2026-09-02 critical GHSA-5ff2-5x9v-v9pw Malicious code in angular-material-panel (npm)Malware npm · angular-material-panel 2026-09-02

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.