NetSight

Security Dashboard

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

Reset
1,611 matching advisories · page 8 of 54Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
critical GHSA-44f6-28pw-q224 Malicious code in beautiful_macaw_z3n (npm)Malware npm · beautiful_macaw_z3n 2026-09-02 critical GHSA-rh58-h25j-6f6m Malicious code in beautiful_hoverfly_z3n (npm)Malware npm · beautiful_hoverfly_z3n 2026-09-02 critical GHSA-xqpq-vcvm-f873 Malicious code in beautiful_antelope-appteadev (npm)Malware npm · beautiful_antelope-appteadev 2026-09-02 critical GHSA-56vv-pmpw-5qjf Malicious code in beautiful_pelican_z3n (npm)Malware npm · beautiful_pelican_z3n 2026-09-02 critical GHSA-238v-whrq-74m7 Malicious code in beautiful_roadrunner_z3n (npm)Malware npm · beautiful_roadrunner_z3n 2026-09-02 critical GHSA-cq4m-jpjr-3cg7 Malicious code in beautiful_planarian_z3n (npm)Malware npm · beautiful_planarian_z3n 2026-09-02 critical GHSA-4r3m-pvg2-qpxc Malicious code in beautiful_catshark_z3n (npm)Malware npm · beautiful_catshark_z3n 2026-09-02 critical GHSA-6g8c-23r8-5ghw Malicious code in beautiful_amphibian_z3n (npm)Malware npm · beautiful_amphibian_z3n 2026-09-02 critical GHSA-8mx7-7x5q-9vf8 Malicious code in beautiful_unicorn-apptea (npm)Malware npm · beautiful_unicorn-apptea 2026-09-02 critical GHSA-2726-2gcx-g5p2 Malicious code in beautiful_rook_z3n (npm)Malware npm · beautiful_rook_z3n 2026-09-02 critical GHSA-g6rw-hwv9-mqfm Malicious code in beautiful_damselfly_0xrequest (npm)Malware npm · beautiful_damselfly_0xrequest 2026-09-02 critical GHSA-xjqm-m3x5-fg2h Malicious code in beautiful_mule_0xrequest (npm)Malware npm · beautiful_mule_0xrequest 2026-09-02 critical GHSA-49g7-fmgx-fwqr Malicious code in beautiful_pike_dumbs (npm)Malware npm · beautiful_pike_dumbs 2026-09-02 critical GHSA-4p5f-587v-fmj8 Malicious code in beautiful_tiger_0xrequest (npm)Malware npm · beautiful_tiger_0xrequest 2026-09-02 critical GHSA-f698-v7c4-whp8 Malicious code in beautiful_canid_z3n (npm)Malware npm · beautiful_canid_z3n 2026-09-02 critical GHSA-qfqj-h8mj-4w82 Malicious code in beag.ly (npm)Malware npm · beag.ly 2026-09-02 critical GHSA-hmf2-hmpf-hccg Malicious code in beam-frontend (npm)Malware npm · beam-frontend 2026-09-02 critical GHSA-g32m-w3xw-mj64 Malicious code in beamlee (npm)Malware npm · beamlee 2026-09-02 critical GHSA-8mw8-pqph-m62x Malicious code in beard-teadev (npm)Malware npm · beard-teadev 2026-09-02 critical GHSA-6xww-mpfj-ch67 Malicious code in beaconlib (npm)Malware npm · beaconlib 2026-09-02 critical GHSA-g9w8-6gc6-8gc5 Malicious code in beacon-labs-translations (npm)Malware npm · beacon-labs-translations 2026-09-02 critical GHSA-mmc7-fg8g-49ph Malicious code in beam-widgets (npm)Malware npm · beam-widgets 2026-09-02 critical GHSA-r2xh-gp7c-pg4m Malicious code in beanstalk-api (npm)Malware npm · beanstalk-api 2026-09-02 critical GHSA-f5wg-53xm-wf7m Malicious code in beautiful-gold-meadowlark (npm)Malware npm · beautiful-gold-meadowlark 2026-09-02 critical GHSA-pwjp-p84f-c8j5 Malicious code in beautiful-jade-sawfish (npm)Malware npm · beautiful-jade-sawfish 2026-09-02 critical GHSA-59v9-m34h-qr64 Malicious code in beautiful-aqua-ape (npm)Malware npm · beautiful-aqua-ape 2026-09-02 critical GHSA-pvc9-jp59-g9j8 Malicious code in beardoze (npm)Malware npm · beardoze 2026-09-02 critical GHSA-qgmj-x6xg-36hr Malicious code in beatrizlima (npm)Malware npm · beatrizlima 2026-09-02 critical GHSA-9qfg-gc34-2cqj Malicious code in basic_bear_z3n (npm)Malware npm · basic_bear_z3n 2026-09-02 critical GHSA-4xf4-2j79-c8qh Malicious code in bad_bear_z3n (npm)Malware npm · bad_bear_z3n 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.