NetSight

Security Dashboard

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

Reset
57 matching advisories · page 2 of 2Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
critical GHSA-frg7-h4qq-x5v8 Malware in ethereum-producerMalware npm · ethereum-producer 2025-02-28 critical GHSA-m2qq-9c9x-gvfh Malware in ethereum-node-crawlerMalware npm · ethereum-node-crawler 2025-02-03 critical GHSA-qj45-2773-r92p Malware in ethereumvulncontracthandlerMalware npm · ethereumvulncontracthandler 2025-01-02 critical GHSA-pg4j-47c5-f23f Malware in lido-on-ethereumMalware npm · lido-on-ethereum 2024-12-27 critical GHSA-fgqj-65jc-pf5v Malware in ethereumjsutilityMalware npm · ethereumjsutility 2024-11-07 critical9.8 CVE-2024-51427 An issue in the PepeGxng smart contract (which can be run on the Ethereum blockchain) allows remote attackers to have an unspecified impact via the mint functi… 2024-10-30 critical9.8 CVE-2024-51424 An issue in the PepeGxng smart contract (which can be run on the Ethereum blockchain) allows remote attackers to have an unspecified impact via the Owned.setOw… 2024-10-30 critical GHSA-x74x-c5cf-wr9p Malware in @huoshanjiebai/ethereumjs-utillMalware npm · @huoshanjiebai/ethereumjs-utill 2023-09-11 critical GHSA-j9xg-8j5w-jf57 Malware in ethereum-cryptographMalware npm · ethereum-cryptograph 2023-09-11 critical GHSA-gxm3-5v88-f48v Malware in ethereum-cryptographyyyMalware npm · ethereum-cryptographyyy 2023-08-08 critical GHSA-w8pp-gwrg-q68c Malware in ethereumjstilMalware npm · ethereumjstil 2022-08-19 critical GHSA-xcv2-39r7-2f4m Malware in ethereumjstoxMalware npm · ethereumjstox 2022-08-19 critical GHSA-grvq-738x-8cjm Malware in ethereum-freeton-bridge-contracts-testMalware npm · ethereum-freeton-bridge-contracts-test 2022-07-25 critical GHSA-5pr5-58cf-fxf4 Malware in ethereum-abiMalware npm · ethereum-abi 2022-06-20 critical GHSA-x35w-7279-wxxv Malware in ethereumjs-utils-oldMalware npm · ethereumjs-utils-old 2022-06-20 critical9.1 CVE-2021-42766 The Proof-of-Stake (PoS) Ethereum consensus protocol through 2021-10-19 allows an adversary to cause a denial of service (long-range consensus chain reorganiza… proof-of-stake_ethereum_project · proof-of-stake_ethereum 2021-10-20 critical9.1 CVE-2021-42764 The Proof-of-Stake (PoS) Ethereum consensus protocol through 2021-10-19 allows an adversary to cause a denial of service (delayed consensus decisions), and als… proof-of-stake_ethereum_project · proof-of-stake_ethereum 2021-10-20 critical GHSA-m6gx-rhvj-fh52 Denial of service in go-ethereum due to CVE-2020-28362 go · github.com/ethereum/go-ethereum 2021-06-29 critical9.8 CVE-2020-17752 Integer overflow vulnerability in payable function of a smart contract implementation for an Ethereum token, as demonstrated by the smart contract implemented … mon_project · mon 2021-06-24 critical10.0 CVE-2017-14451 An exploitable out-of-bounds read vulnerability exists in libevm (Ethereum Virtual Machine) of CPP-Ethereum. ethereum · ethereum 2020-12-02 critical9.8 CVE-2018-15890 Deserialization of Untrusted Data in EthereumJ maven · org.ethereum:ethereumj-core 2019-06-20 critical9.8 CVE-2018-17111 The onlyOwner modifier of a smart contract implementation for Coinlancer (CL), an Ethereum ERC20 token, has a potential access control vulnerability. coinlancer · coinlancer 2018-09-18 critical9.8 CVE-2018-14088 An issue was discovered in a smart contract implementation for STeX White List (STE(WL)), an Ethereum token. stex_white_list_project · stex_white_list 2018-07-16 critical9.8 CVE-2018-14087 An issue was discovered in a smart contract implementation for EUC (EUC), an Ethereum token. encryptedtoken_project · encryptedtoken 2018-07-16 critical9.8 CVE-2018-14086 An issue was discovered in a smart contract implementation for SingaporeCoinOrigin (SCO), an Ethereum token. mytoken_project · mytoken 2018-07-16 critical9.8 CVE-2018-14084 An issue was discovered in a smart contract implementation for MKCB, an Ethereum token. myadvancedtoken_project · myadvancedtoken 2018-07-16 critical9.8 CVE-2018-14063 The increaseApproval function of a smart contract implementation for Tracto (TRCT), an Ethereum ERC20 token, has an integer overflow. tracto · tracto 2018-07-15

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.