Ce mail provient de l'extérieur, restons vigilants

=====================================================================

                            CERT-Renater

                Note d'Information No. 2025/VULN613
_____________________________________________________________________

DATE                : 16/09/2025

HARDWARE PLATFORM(S): /

OPERATING SYSTEM(S): Systems running debug (npm) versions prior to
                                         4.4.3.

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


debug@4.4.2 contains malware after npm account takeover
Critical
Qix- published GHSA-4x49-vf9v-38px Sep 15, 2025

Package
debug (npm)

Affected versions
4.4.2

Patched versions
4.4.3


Description

Impact

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 <script> 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. See references below for more information
on the payload.


Patches

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. This version is functionally
identical to the previously known-good version, published as a
patch version bump above the compromised version.

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.


References

    https://www.aikido.dev/blog/npm-debug-and-chalk-packages-compromised
    https://socket.dev/blog/npm-author-qix-compromised-in-major-supply-chain-attack
    https://www.ox.security/blog/npm-packages-compromised/


Point of Contact

In the event suspicious behavior is still observed for the package
listed in this security advisory after performing all of the above
cleaning operations (see Patches above), please reach out via one
of the following channels of communication:

    Bluesky, package owner: https://bsky.app/profile/bad-at-computer.bsky.social
    debug repository, tracking issue (applies to all packages affected in the breach): #1005


Severity
Critical

CVE ID
CVE-2025-59144

Weaknesses
Weakness CWE-506


=========================================================
+ CERT-RENATER        |    tel : 01-53-94-20-44         +
+ 23/25 Rue Daviel    |    fax : 01-53-94-20-41         +
+ 75013 Paris         |   email:cert@support.renater.fr +
=========================================================