# Security notice: AsyncAPI npm supply chain compromise — Mintlify is not affected

- Provider: [Mintlify](https://down.guide/mintlify)
- Level: confirmed
- Impact: Degraded
- lasted 0m
- started 2026-07-16 18:54 UTC
- id: DWN-9fc9193edd
- Official page: https://status.mintlify.com/incidents/01KXP4FTZQ87AQY95MPB5Y04C8

## Updates from Mintlify
### 2026-07-16 18:54 UTC: resolved
On July 14, 2026, several packages in the \`@asyncapi\` npm namespace were compromised in a supply chain attack. An attacker exploited a misconfigured GitHub Actions workflow in the AsyncAPI generator repository to steal a publish token and release malicious versions of \`@asyncapi/specs\` (6.11.2, 6.11.2-alpha.1), \`@asyncapi/generator\` (3.3.1), \`@asyncapi/generator-components\` (0.7.1), and \`@asyncapi/generator-helpers\` (1.1.1).
We reviewed our dependency tree and confirmed Mintlify is not affected:
- We do not use \`@asyncapi/generator\`, \`@asyncapi/generator-helpers\`, or \`@asyncapi/generator-components\` anywhere in our codebase.
- The only \`@asyncapi\` packages we depend on are \`@asyncapi/parser\` (not compromised) and \`@asyncapi/specs\`, which our lockfiles pin at 6.11.1 and 6.8.1 — both below the compromised 6.11.2. We will keep specs pinned below 6.11.2.
- The malicious versions were never installed in our development, CI, or production environments, and we found no signs of impact.
Mintlify's AsyncAPI documentation features continue to work normally and were never at risk. No action is required on your part.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by Sazabi (https://sazabi.com/?utm_source=down-guide&utm_medium=markdown).