3gr2dj

Ecosystem: npm

Downloads:

Vulnerabilities from the last (months)
  • 0CriticalAffects 0 versions
  • 0HighAffects 0 versions
  • 0MediumAffects 0 versions
  • 0ModerateAffects 0 versions
  • 0LowAffects 0 versions
Severity distribution (all time)
0vulnerabilities
  • Critical0 (0.0%)
  • High0 (0.0%)
  • Medium0 (0.0%)
  • Moderate0 (0.0%)
  • Low0 (0.0%)

Monthly breakdown

  • 0 vulnerabilities
    • Critical: 0
    • High: 0
    • Medium: 0
    • Moderate: 0
    • Low: 0

Vulnerabilities (1)

Known vulnerabilities affecting 3gr2dj, based on data from OSV.

Vulnerabilities affecting 3gr2dj
IDSeveritySummaryAffected versionsPublishedSource
MAL-2026-17945UnknownMalicious code in 3gr2dj (npm)--- _-= Per source details. Do not edit below this line.=-_ ## Source: ghsa-malware (d22fac2aefcc35b1e53218b222078517b198a09f3264326027a3772237787136) 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.
  • all
OSV (opens in a new tab)
  • MAL-2026-17945Unknown
    Malicious code in 3gr2dj (npm)
    • all

    --- _-= Per source details. Do not edit below this line.=-_ ## Source: ghsa-malware (d22fac2aefcc35b1e53218b222078517b198a09f3264326027a3772237787136) 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.

Showing 1-1 of 1 vulnerabilities