vybscan-testbed-obfuscated-postinstall

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 vybscan-testbed-obfuscated-postinstall, based on data from OSV.

Vulnerabilities affecting vybscan-testbed-obfuscated-postinstall
IDSeveritySummaryAffected versionsPublishedSource
MAL-2026-10079UnknownMalicious code in vybscan-testbed-obfuscated-postinstall (npm)--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (cf9aee5b150e0606b1c5c2469fdab43496965a3dd5664df288d68d618e326567) package.json declares a postinstall lifecycle script that runs `node -e "eval(Buffer.from('<base64>','base64').toString())"`. Installing the package triggers execution of code that is not visible in the package source and is only materialized at install time by decoding an opaque literal. In this specific version the decoded blob is an inert console.log, but the mechanism — obfuscated-then-eval'd bytes wired into a lifecycle hook — is the c
  • all
OSV (opens in a new tab)
  • MAL-2026-10079Unknown
    Malicious code in vybscan-testbed-obfuscated-postinstall (npm)
    • all

    --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (cf9aee5b150e0606b1c5c2469fdab43496965a3dd5664df288d68d618e326567) package.json declares a postinstall lifecycle script that runs `node -e "eval(Buffer.from('<base64>','base64').toString())"`. Installing the package triggers execution of code that is not visible in the package source and is only materialized at install time by decoding an opaque literal. In this specific version the decoded blob is an inert console.log, but the mechanism — obfuscated-then-eval'd bytes wired into a lifecycle hook — is the c

Showing 1-1 of 1 vulnerabilities