CVE-2025-59144

HIGHNVD 8.88.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.5% (41st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2025-29226 (ENISA EUVD) · GHSA-4x49-vf9v-38px (GitHub Security Advisories)Source: ENISA EUVD

8.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 8.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

debug is a JavaScript debugging utility. On 8 September 2025, the npm publishing account for debug was taken over after a phishing attack. Version 4.4.2 was published, functionally identical to the previous patch version, but with a malware payload added attempting to redirect cryptocurrency transactions to the attacker's own addresses from within browser environments. Local environments, server environments, command line applications, etc. are not affected. If the package was used in a browser context (e.g. a direct inclusion, or via a bundling tool such as Babel, Rollup, Vite, Next.js, etc.) there is a chance the malware still exists and such bundles will need to be rebuilt. The malware seemingly only targets cryptocurrency transactions and wallets such as MetaMask. npm removed the offending package from the registry over the course of the day on 8 September, preventing further downloads from npm proper. On 13 September, the package owner published new patch versions to help cache-bust those using private registries who might still have the compromised version cached. Users should upgrade to the latest patch version, completely remove their node_modules directory, clean their package manager's global cache, and rebuild any browser bundles from scratch. Those operating private registries or registry mirrors should purge the offending versions from any caches. This issue has been resolved in 4.4.3.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
55
EG Risk 55/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity88% × 45%
Impact severity (EG Severity): CVSS 8.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
41st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.8): severity, escalated by confirmed exploitation. This CVE's 8.8 is its impact severity (EG Severity), not escalated.

EG Severity
8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 15, 2025

Last Modified

October 19, 2026

Advisory Details (5)

Auto-updated Aug 13, 2026
Patch available. Sources: github.
Web page

19 npm Packages Compromised in Major Supply-Chain Attack | OX Security

https://www.ox.security/blog/npm-packages-compromised
Web page

npm debug and chalk packages compromised

https://www.aikido.dev/blog/npm-debug-and-chalk-packages-compromised
Web page

npm Author Qix Compromised via Phishing Email in Major Supply Chain Attack | Socket

https://socket.dev/blog/npm-author-qix-compromised-in-major-supply-chain-attack
GitHub advisoryMentions a patch (unverified)

debug@4.4.2 contains malware after npm account takeover · Advisory · debug-js/debug · GitHub

https://github.com/debug-js/debug/security/advisories/GHSA-4x49-vf9v-38px
Web page

(RESOLVED) Version 4.4.2 published to npm is compromised · Issue #1005 · debug-js/debug · GitHub

https://github.com/debug-js/debug/issues/1005

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npmdebug @ 4.4.3 (fixes = 4.4.2)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
debug4.4.2
  • 4.4.2 up to 4.4.3: fixed in 4.4.3
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 41× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 95 of 220 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 5 repeat rows among the latest 100 are merged into the row they repeat. The 125 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  2. 2026-11-01 08:03 UTCGHSA enrichmentGHSA-4x49-vf9v-38px · GitHub severity HIGH
  3. 2026-11-01 08:03 UTCEG score recompute
  4. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  5. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  6. 2026-10-29 16:31 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  7. 2026-10-29 03:34 UTCEG score recompute
  8. 2026-10-28 16:30 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  9. 2026-10-27 16:30 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  10. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  11. 2026-10-25 16:31 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  12. 2026-10-25 16:16 UTCEG score recompute
  13. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  14. 2026-10-23 16:30 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  15. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  16. 2026-10-22 11:32 UTCEG score recompute
  17. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  18. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  19. 2026-10-19 17:29 UTCEG score recompute
  20. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  21. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  22. 2026-10-18 05:23 UTCEG score recompute
  23. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  24. 2026-10-16 16:39 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  25. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.4% · 37th percentile
Show 70 more
  1. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  2. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  3. 2026-10-12 16:53 UTCEG score recompute
  4. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  5. 2026-10-11 20:28 UTCEG score recompute
  6. 2026-10-11 18:39 UTCEG score recompute
  7. 2026-10-11 15:14 UTCEG score recompute
  8. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  9. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  10. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  11. 2026-10-08 17:10 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  12. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  13. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  14. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  15. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  16. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  17. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  18. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  19. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  20. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  21. 2026-09-26 00:25 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  22. 2026-09-24 14:02 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  23. 2026-09-23 16:24 UTCEG score recompute
  24. 2026-09-23 13:47 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  25. 2026-09-21 21:06 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  26. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  27. 2026-09-19 15:42 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  28. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  29. 2026-09-17 19:29 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  30. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  31. 2026-09-16 05:14 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  32. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  33. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  34. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  35. 2026-09-11 09:36 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  36. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  37. 2026-09-08 21:59 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  38. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  39. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  40. 2026-09-05 15:28 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  41. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  42. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  43. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  44. 2026-09-01 04:38 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  45. 2026-08-30 19:16 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  46. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  47. 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  48. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  49. 2026-08-26 14:45 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  50. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  51. 2026-08-24 14:16 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  52. 2026-08-24 09:22 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  53. 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  54. 2026-08-21 23:48 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  55. 2026-08-20 22:54 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  56. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  57. 2026-08-18 13:47 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  58. 2026-08-17 13:46 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  59. 2026-08-16 14:55 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  60. 2026-08-16 02:13 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  61. 2026-08-15 01:29 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  62. 2026-08-13 21:59 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  63. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  64. 2026-08-11 13:42 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  65. 2026-08-10 23:59 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  66. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  67. 2026-08-08 16:36 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  68. 2026-08-07 16:26 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  69. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  70. 2026-08-05 19:16 UTCEPSS rescoreEPSS 0.4% · 30th percentile

Frequently asked(5)

What is CVE-2025-59144?
CVE-2025-59144 is a high-severity vulnerability; its CVE record was published on September 15, 2025. debug is a JavaScript debugging utility. On 8 September 2025, the npm publishing account for debug was taken over after a phishing attack. Version 4.4.2 was published, functionally identical to the previous patch version, but with a malware payload added attempting to redirect cryptocurrency…
When was the CVE record for CVE-2025-59144 published?
The CVE record for CVE-2025-59144 was published on September 15, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 19, 2026; the record at its source may have been updated since.
Is CVE-2025-59144 actively exploited?
CVE-2025-59144 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (41st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-59144?
CVE-2025-59144 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2025-59144?
A fix for CVE-2025-59144 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-59144

Explore →

Is Your Infrastructure Affected by CVE-2025-59144?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.