Commit d2c1983
security(deps): pin @asyncapi packages to non-compromised versions
Several AsyncAPI npm packages were briefly compromised on 2026-07-14
(the "Miasma RAT" supply-chain incident, delivered via a post-install
sync.js dropper). sei-js pulls @asyncapi/specs transitively through
mint -> @asyncapi/parser, whose "^6.8.0" range can float up into the
compromised 6.11.2 on any fresh install or lockfile regeneration.
Pin the four affected packages to their latest non-compromised
versions via pnpm.overrides so no install can resolve a malicious
release:
@asyncapi/specs 6.11.1 (in tree: 6.10.0 -> 6.11.1)
@asyncapi/generator 3.3.0 (preventive; not in tree)
@asyncapi/generator-helpers 1.1.0 (preventive; not in tree)
@asyncapi/generator-components 1.0.0 (preventive; not in tree)
No compromised version was ever present in the lockfile. The only
resolved change is @asyncapi/specs 6.10.0 -> 6.11.1; the generator
pins are defense-in-depth in case that toolchain is introduced later.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>1 parent bc17ace commit d2c1983
2 files changed
Lines changed: 30 additions & 7 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
25 | 25 | | |
26 | 26 | | |
27 | 27 | | |
28 | | - | |
| 28 | + | |
| 29 | + | |
| 30 | + | |
| 31 | + | |
| 32 | + | |
| 33 | + | |
| 34 | + | |
| 35 | + | |
| 36 | + | |
29 | 37 | | |
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.
0 commit comments