NetSight

Security Dashboard

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

Reset
434 matching advisories · page 4 of 15Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
critical GHSA-xc29-xrpm-gp63 Malicious code in equinox-centauri-lacerta-callisto (npm)Malware npm · equinox-centauri-lacerta-callisto 2026-09-10 critical GHSA-jpxq-cmqf-4v44 Malicious code in epimetheus-triton-lacerta-altair (npm)Malware npm · epimetheus-triton-lacerta-altair 2026-09-10 critical GHSA-cfv2-g7cq-278w Malicious code in epigenetics-centauri-lacerta-primatology (npm)Malware npm · epigenetics-centauri-lacerta-primatology 2026-09-10 critical GHSA-cqf4-6fq7-7mxg Malicious code in enif-spectron-webdriver-quasar-lacerta (npm)Malware npm · enif-spectron-webdriver-quasar-lacerta 2026-09-10 critical GHSA-h38m-8xfj-qm3v Malicious code in enif-gatsby-fetch-lacerta (npm)Malware npm · enif-gatsby-fetch-lacerta 2026-09-10 critical GHSA-vfhv-5hv6-gv9p Malicious code in eleventy-lacerta-private-alphard (npm)Malware npm · eleventy-lacerta-private-alphard 2026-09-10 critical GHSA-2879-fjvx-27wv Malicious code in dysonswarm-lacerta-unuk-dynamo (npm)Malware npm · dysonswarm-lacerta-unuk-dynamo 2026-09-06 critical GHSA-6r8v-f6qv-w7pq Malicious code in duplex-lacerta-link-pipe (npm)Malware npm · duplex-lacerta-link-pipe 2026-09-06 critical GHSA-pv94-59xp-9m2p Malicious code in draco-lacerta-process-semantic-ui (npm)Malware npm · draco-lacerta-process-semantic-ui 2026-09-06 critical GHSA-4h43-8x4j-f962 Malicious code in down_load_ebook_branding_lo_que_necesita_saber_acerca_de_la_const_by_chase_barlow_patbz (npm)Malware npm · down_load_ebook_branding_lo_que_necesita_saber_acerca_de_la_const_by_chase_barlow_patbz 2026-09-06 critical GHSA-jmw6-cvgf-rh44 Malicious code in dotenv-safe-ultra-lacerta-cors (npm)Malware npm · dotenv-safe-ultra-lacerta-cors 2026-09-06 critical GHSA-mf8p-jxxg-8wqx Malicious code in docusaurus-cladistics-version-lacerta (npm)Malware npm · docusaurus-cladistics-version-lacerta 2026-09-06 critical GHSA-hpxx-ghww-p6jp Malicious code in dependencies-lacerta-hermes-install (npm)Malware npm · dependencies-lacerta-hermes-install 2026-09-06 critical GHSA-jwcw-48qp-m77c Malicious code in dagda-deimos-janus-lacerta (npm)Malware npm · dagda-deimos-janus-lacerta 2026-09-04 critical GHSA-cgww-h6h6-8grj Malicious code in dactyl-loopback-axios-lacerta (npm)Malware npm · dactyl-loopback-axios-lacerta 2026-09-04 critical GHSA-f9g3-ghr9-w76f Malicious code in dactyl-lacerta-inquirer-scorpius (npm)Malware npm · dactyl-lacerta-inquirer-scorpius 2026-09-04 critical GHSA-76xg-rcg5-px96 Malicious code in cz-conventional-changelog-blitz-steganography-lacerta (npm)Malware npm · cz-conventional-changelog-blitz-steganography-lacerta 2026-09-04 critical GHSA-q7pf-gcw5-78h5 Malicious code in csrf-commitlint-config-angular-axios-lacerta (npm)Malware npm · csrf-commitlint-config-angular-axios-lacerta 2026-09-04 critical GHSA-523f-3h48-4qmc Malicious code in cosmochemistry-lacerta-magnetosphere-reveal-md (npm)Malware npm · cosmochemistry-lacerta-magnetosphere-reveal-md 2026-09-04 critical GHSA-424h-f3gr-rxr4 Malicious code in convict-cypress-lacerta-postcss (npm)Malware npm · convict-cypress-lacerta-postcss 2026-09-04 critical GHSA-c6jw-mjx5-vh25 Malicious code in config-event-install-lacerta (npm)Malware npm · config-event-install-lacerta 2026-09-04 critical GHSA-3q59-fgfg-hg9w Malicious code in command-adonis-colors-lacerta (npm)Malware npm · command-adonis-colors-lacerta 2026-09-04 critical GHSA-723g-98h9-7ww9 Malicious code in comet-lacerta-config-atlas (npm)Malware npm · comet-lacerta-config-atlas 2026-09-04 critical GHSA-4v68-wrh3-qjm9 Malicious code in colors-lacerta-dotenv-safe-xenon (npm)Malware npm · colors-lacerta-dotenv-safe-xenon 2026-09-04 critical GHSA-g7xr-h4j7-55cc Malicious code in chalk-magellan-lacerta-request (npm)Malware npm · chalk-magellan-lacerta-request 2026-09-04 critical GHSA-fv98-g7hg-m8gr Malicious code in chakra-ui-lacerta-tethys-protractor (npm)Malware npm · chakra-ui-lacerta-tethys-protractor 2026-09-04 critical GHSA-qg57-v48x-vhmh Malicious code in ceres-cressida-lacerta-foundation (npm)Malware npm · ceres-cressida-lacerta-foundation 2026-09-04 critical GHSA-6fc6-mgfj-xpv8 Malicious code in centauri-lacerta-config-taurus (npm)Malware npm · centauri-lacerta-config-taurus 2026-09-04 critical GHSA-8529-7259-cxx3 Malicious code in babel-development-jabbah-lacerta (npm)Malware npm · babel-development-jabbah-lacerta 2026-09-02 critical GHSA-3hqq-8g3g-c72m Malicious code in await-lacerta-ganymede-commitizen (npm)Malware npm · await-lacerta-ganymede-commitizen 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.