0xlr-stripe-frontend

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 0xlr-stripe-frontend, based on data from OSV.

Vulnerabilities affecting 0xlr-stripe-frontend
IDSeveritySummaryAffected versionsPublishedSource
MAL-2026-5389UnknownMalicious code in @0xlr/stripe-frontend (npm)--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (3eda7bf8681a6253ffc4bc965888e45c5374e4ba8d4fe2e17efcd0f227d7ce5e) On `npm install`, postinstall.js enumerates every entry in process.env (sorted), bundles it with hostname, username, homedir, cwd, argv, and platform/arch, and POSTs the JSON payload over HTTPS to the hardcoded Burp Collaborator subdomain rytxau88zxh61dw6qz4yn19naeg54vsk.oastify.com. Any tokens present in the install environment (AWS, GCP, CI tokens, npm tokens, etc.) are leaked to the attacker. The package's own metadata describes itself a
  • all
OSV (opens in a new tab)
  • MAL-2026-5389Unknown
    Malicious code in @0xlr/stripe-frontend (npm)
    • all

    --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (3eda7bf8681a6253ffc4bc965888e45c5374e4ba8d4fe2e17efcd0f227d7ce5e) On `npm install`, postinstall.js enumerates every entry in process.env (sorted), bundles it with hostname, username, homedir, cwd, argv, and platform/arch, and POSTs the JSON payload over HTTPS to the hardcoded Burp Collaborator subdomain rytxau88zxh61dw6qz4yn19naeg54vsk.oastify.com. Any tokens present in the install environment (AWS, GCP, CI tokens, npm tokens, etc.) are leaked to the attacker. The package's own metadata describes itself a

Showing 1-1 of 1 vulnerabilities