Mitigating the Axios npm supply chain compromise
A post on microsoft.com is cited by 20 distinct blogs to date (corpus.blog, measured 16 October 2026).
A record is what was published and who pointed at it. The text of the post is not shown here: read it at the source, or at its Wayback capture.
20blogs citing
| Period | Blogs | Links |
|---|---|---|
| All time | 20 | 20 |
| Last 90 days | 2 | 2 |
| Last 30 days | 2 | 2 |
| Last 7 days | 0 | 0 |
| First cited | 25 Mar 2026 |
|---|---|
| Latest citation | 7 Oct 2026 |
| Words blogs link it with | 5 |
| External links | 6 |
| Length | 3,408 |
0 this week (still settling) · peak 4
Show as table
| Week of | Value |
|---|---|
| 23 Mar 2026 | 1 |
| 30 Mar 2026 | 4 |
| 6 Apr 2026 | 3 |
| 13 Apr 2026 | 2 |
| 20 Apr 2026 | 1 |
| 27 Apr 2026 | 0 |
| 4 May 2026 | 2 |
| 11 May 2026 | 2 |
| 18 May 2026 | 1 |
| 25 May 2026 | 0 |
| 1 Jun 2026 | 1 |
| 8 Jun 2026 | 0 |
| 15 Jun 2026 | 0 |
| 22 Jun 2026 | 0 |
| 29 Jun 2026 | 0 |
| 6 Jul 2026 | 0 |
| 13 Jul 2026 | 0 |
| 20 Jul 2026 | 0 |
| 27 Jul 2026 | 0 |
| 3 Aug 2026 | 0 |
| 10 Aug 2026 | 0 |
| 17 Aug 2026 | 0 |
| 24 Aug 2026 | 0 |
| 31 Aug 2026 | 0 |
| 7 Sept 2026 | 0 |
| 14 Sept 2026 | 0 |
| 21 Sept 2026 | 0 |
| 28 Sept 2026 | 1 (still settling) |
| 5 Oct 2026 | 1 (still settling) |
| 12 Oct 2026 | 0 (still settling) |
Each blog counts once, in the week of its first citation. 1 blog has no dated post that cites this page: counted in the tally, not here. A blog added to the index recently can bring old first citations in at once.
Who cited it
BetaCited by 20 blogs across 1 subject: technology 14, unclassified 6.
- Technology14
- Unclassified6
Words blogs link it with
The words blogs link this page with, by how many different blogs use them.
- axios3 blogs
- axios compromise1 blog
- axios got poisoned1 blog
- axios incident1 blog
- happened to axios1 blog
Cited by 20 blogs in 20 posts
One row per blog, the most recently citing first. Each shows the blog's newest citing post; open a row for the others.
linked as “Axios Compromise”
Read at unit42.paloaltonetworks.com (opens in a new tab)linked as “shipped two poisoned releases”
Read at lazutkin.com (opens in a new tab)linked as “Axios”
Read at dedoimedo.com (opens in a new tab)linked as “Mitigating the Axios npm supply chain compromise (Microsoft Security Blog)”
Read at radval.me (opens in a new tab)linked as “North Korean state actors compromised Axios”
Read at janbrennenstuhl.eu (opens in a new tab)linked as “malicious payload”
Read at netflux.io (opens in a new tab)linked as “supply chain compromise”
Read at rapid7.com (opens in a new tab)linked as “triggered a separate script”
Read at cloudfest.com (opens in a new tab)linked as “slow down how quickly you upstream package updates”
Read at cory.news (opens in a new tab)linked as “happened to Axios”
Read at hollandtech.net (opens in a new tab)linked as “Axios incident”
Read at luca-becker.me (opens in a new tab)linked as “Mitigating the Axios npm supply chain compromise Microsoft — Axios (70M weekly downloads) got backdo…”
Read at 8a03e7a6.c-b-io.pages.dev (opens in a new tab)linked as “Microsoft: Mitigating the Axios npm Supply Chain Compromise”
Read at safedep.io (opens in a new tab)linked as “Microsoft has a good post with more details”
Read at sixlines.org (opens in a new tab)linked as “axios got poisoned”
Read at ahmet.ee (opens in a new tab)linked as “Microsoft Security”
Read at stepsecurity.io (opens in a new tab)Links from this post
Elsewhere on microsoft.com (24)
Looking for more like this? Find posts and blogs like it
Something wrong here? Report a problem