imo-allowlist-xss-poc

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 imo-allowlist-xss-poc, based on data from OSV.

Vulnerabilities affecting imo-allowlist-xss-poc
IDSeveritySummaryAffected versionsPublishedSource
MAL-2026-14559UnknownMalicious code in imo-allowlist-xss-poc (npm)--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (76f429a987c3b4800204131b27faae0c29e55a0761a1fa2a0306ab14a343afd7) The package was found to contain malicious code or consuming dependency that contains malicious code ## Source: ghsa-malware (313a05ec020f006e78cf6f6a7bb0e1885c23003844a2f13d8ad6ac215736f4f2) 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
  • all
OSV (opens in a new tab)
  • MAL-2026-14559Unknown
    Malicious code in imo-allowlist-xss-poc (npm)
    • all

    --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (76f429a987c3b4800204131b27faae0c29e55a0761a1fa2a0306ab14a343afd7) The package was found to contain malicious code or consuming dependency that contains malicious code ## Source: ghsa-malware (313a05ec020f006e78cf6f6a7bb0e1885c23003844a2f13d8ad6ac215736f4f2) 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

Showing 1-1 of 1 vulnerabilities