npm package report

Is debug safe?

Version 4.4.2 of debug was compromised; other versions are not flagged as malicious. CyberXYZ Proxy blocks the affected versions. It also has 3 known vulnerabilities, the worst rated HIGH.

Do not install debug 4.4.2

CRITICAL

Compromised releases. Added to CyberXYZ 2025-09-08, OSV malicious-package feed (Google / OpenSSF).

// what we observed

The package was compromised and malicious code added. Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Reported by GitHub Advisory Database via OSV.

// versions and what to do
Malicious
4.4.2
Move to
4.4.3 newest 4.x release, no known advisory

If one of these versions was installed, remove it and treat the credentials, tokens and SSH keys on that machine as exposed: rotate them. Check CI runners and container images that installed it too.

npm install debug@4.4.3

OSV recordreferenceadvisoryissueadvisoryadvisory

// reach

1 direct dependencies

1 carry known advisories, worst HIGH

1,712 packages depend on it

an advisory here reaches each of them

Create a free accountfor every dependency path, dependent and what to upgrade
// ai model usage

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


cvss
8.8
high

CVSS v4.0 base score out of 10

epss
0.50%
medium

chance of exploitation in 30 days, 43rd percentile of all CVEs

xyz score
5.3
medium

CyberXYZ composite out of 10

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

// 3 advisories

On 8 September 2025, the npm publishing account for debug was taken over after a phishing attack.

Full advisory text at GitHub advisory or NVD.

// cvss v4.0 vector

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N/E:A/U:Red

Attack vector
Network
Attack complexity
Low
Attack requirements
None
Privileges required
None
User interaction
None
Confidentiality (vulnerable system)
Low
Integrity (vulnerable system)
High
Availability (vulnerable system)
None
Confidentiality (subsequent systems)
None
Integrity (subsequent systems)
None
Availability (subsequent systems)
None
Exploit maturity
Attacked
U
Red
// questions
Is debug safe to install?

Version 4.4.2 of debug was compromised. Other versions are not flagged as malicious.

Does debug have known vulnerabilities?

Yes. CyberXYZ records 3 known vulnerabilities for debug (npm), the worst rated HIGH. They are GHSA-4x49-vf9v-38px, GHSA-9vvw-cc9w-f27h, GHSA-gxpj-cx7g-858c.

Which version of debug should I use?

Use 4.4.3 or a later release that is not named as malicious. Versions named on this report as malicious must not be installed.

How do I check debug before installing?

Search debug in CyberXYZ Check at https://cyberxyz.io/check?q=debug. The xyz Scanner checks a project's dependencies, and CyberXYZ Proxy checks each package as it is installed.


Checked 2026-11-17 at 13:59 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.