Live › incident › INC-npm-b0f9jxcs1b67

mediumVendorresolved

npm: Incident with npm registry and website affecting logins and publishing

Not triaged yet. The sources’ own description is below.

Known so far

1/6

medium

no CVSS yet; severity from the sources

known so far1 of 6

missing: versions, how to check, fix, exploitation, summary

First public: Aug 7, 2025 UTC
Last modified: Aug 7, 2025
Status: resolved
Known exploitation: None reported
Public exploit: None on GitHub
EPSS: not scored

First seen by InfraStack 2026-10-23 19:12 UTC. All times on this page are UTC.

Who is affected

1 product

Product	Ecosystem	Affected	Fixed in
npm	vendor	–	–

Who cares: incident, npm, ops, registry
Not affected if: –

How to check

Unknown from the sources.

The fix

Unknown from the sources.

Who had it, and when

1 source

status page2026-10-23 19:12 UTC · published 2025-08-07 22:31 UTC · npm:b0f9jxcs1b67

Each row is the first time that source carried this signal. The analyst’s rows are its own findings.

Know the next one before it finds you.

Add to Slack

Live › incident › INC-npm-b0f9jxcs1b67

Go to dashboard

mediumVendorresolved

npm: Incident with npm registry and website affecting logins and publishing

Not triaged yet. The sources’ own description is below.

Known so far

1/6

medium

no CVSS yet; severity from the sources

known so far1 of 6

missing: versions, how to check, fix, exploitation, summary

First public: Aug 7, 2025 UTC
Last modified: Aug 7, 2025
Status: resolved
Known exploitation: None reported
Public exploit: None on GitHub
EPSS: not scored

First seen by InfraStack 2026-10-23 19:12 UTC. All times on this page are UTC.

Who is affected

1 product

Product	Ecosystem	Affected	Fixed in
npm	vendor	–	–

Who cares: incident, npm, ops, registry
Not affected if: –

How to check

Unknown from the sources.

The fix

Unknown from the sources.

Who had it, and when

1 source

status page2026-10-23 19:12 UTC · published 2025-08-07 22:31 UTC · npm:b0f9jxcs1b67

Each row is the first time that source carried this signal. The analyst’s rows are its own findings.

Know the next one before it finds you.

Add to Slack

npm: Incident with npm registry and website affecting logins and publishing

Who is affected

How to check

The fix

Who had it, and when

Know the next one before it finds you.

npm: Incident with npm registry and website affecting logins and publishing

Who is affected

How to check

The fix

Who had it, and when

Know the next one before it finds you.

What the sources say, verbatim

Sources