Skip to content

Commit d2c1983

Browse files
alexander-seiclaude
andcommitted
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

File tree

package.json

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,5 +25,13 @@
2525
"ts-node": "2.1.2",
2626
"typescript": "^5.8.2"
2727
},
28-
"packageManager": "pnpm@9.0.0"
28+
"packageManager": "pnpm@9.0.0",
29+
"pnpm": {
30+
"overrides": {
31+
"@asyncapi/specs": "6.11.1",
32+
"@asyncapi/generator": "3.3.0",
33+
"@asyncapi/generator-helpers": "1.1.0",
34+
"@asyncapi/generator-components": "1.0.0"
35+
}
36+
}
2937
}

pnpm-lock.yaml

Lines changed: 21 additions & 6 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

0 commit comments

Comments
 (0)