Homepage

Embedded Malicious Code Affecting dotnet-sdk-6.0-source-built-artifacts package, versions *

Severity

 Recommended
high

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.07% (22nd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL9-DOTNETSDK60SOURCEBUILTARTIFACTS-14078206
  • published25 Nov 2025
  • disclosed15 Sept 2025
Report a new vulnerability Found a mistake?

Introduced: 15 Sep 2025

Malicious CVE-2025-59144  (opens in a new tab)
CWE-506  (opens in a new tab)

How to fix?

There is no fixed version for RHEL:9 dotnet-sdk-6.0-source-built-artifacts.

NVD Description

Note: Versions mentioned in the description apply only to the upstream dotnet-sdk-6.0-source-built-artifacts package and not the dotnet-sdk-6.0-source-built-artifacts package as distributed by RHEL. See How to fix? for RHEL:9 relevant fixed versions and status.

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 <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. 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.