npm package report

Is debug safe?

3 known vulnerabilities, worst severity HIGH.

cvss
8.8

how bad it is if exploited, out of 10

epss
0.40%

chance of exploitation in the next 30 days

xyz score
5.3

CyberXYZ composite, out of 10

fig. 01 — GHSA-4x49-vf9v-38px, the advisory selected below

// advisories

GHSA-4x49-vf9v-38px

HIGHCVE-2025-59144

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.

Affected
= 4.4.2
Fixed in
4.4.3
Weakness
CWE-506
Published
2025-09-15
Source
github

GHSANVDMITREreferencereferencereferencereferencereference

// dependencies

1 direct, 1 carrying known advisories, worst HIGH

Sign in for dependency paths and remediation

// ai model usage

Tracked for PyPI packages. HuggingFace models declare Python dependencies, so npm packages are not covered.

Checked 2026-09-22 at 01:31 UTC. The most recent advisory here was published 2025-09-15. Updated continuously from NVD, GHSA, OSV and CNA feeds.

Think a verdict here is wrong? Tell us — we respond within 2 business days.
Is debug safe? npm package security report | CyberXYZ