advisory-catalog: openapi-react-query-codegen-2026-08-28

[ronheichman]

Adds a Bumblebee threat_intel catalog for the Mini Shai-Hulud npm supply-chain compromise of @7nohe/openapi-react-query-codegen, reported by Socket on 2026-08-28.

Source: https://socket.dev/blog/openapi-react-query-codegen-npm-compromise (date_published: 2026-08-28T20:49:35Z)

Compromised versions (10):

• 0.0.0-365d4eb738d3146583431948d3ba6e27a32556be
• 0.0.0-ec7876d6c917dad516ba69bbfafc948b834bf0ab
• 0.5.4, 0.5.5
• 1.6.3, 1.6.4
• 2.2.1, 2.2.2
• 3.0.3, 3.0.4

Last known-good version per release line: 0.5.3, 1.6.2, 2.2.0, 3.0.2.

Public corroboration (two non-origin sources):

1. npm registry — https://registry.npmjs.org/@7nohe/openapi-react-query-codegen: all 10 versions present with publication timestamps 2026-08-28T20:00Z-20:20Z, matching Socket's two-wave timing.
2. deps.dev — https://api.deps.dev/v3/systems/npm/packages/%407nohe%2Fopenapi-react-query-codegen/versions/<v>: confirms the same publication timestamps for the 3.0.4 / 2.2.2 / 1.6.4 / 0.5.5 wave-2 versions (spot-checked).

OSV (api.osv.dev/v1/query on npm) and the GitHub Advisory Database (GET /advisories?ecosystem=npm&type=malware) had no entries for this package at the time of cataloging; expected to populate as MAL-/GHSA- ids are issued. This will not delay publication given the strong registry-side corroboration.

Yank observation: none — all 10 malicious versions were still installable at the time of the Socket post and at the time of cataloging.

Ecosystem-enum note: none — npm is in the schema enum, and the catalog uses entries[] as normal (no _<ecosystem>_packages fallback needed).

Dropped items: none — every (ecosystem, package, version) claim in the Socket post is present in entries[0].versions.

Root cause per Socket (not encoded in this catalog): release.yml triggered on issue_comment: [created] and gated only on comment text; any GitHub account could publish a fork's contents under the repo's trusted-publishing identity by commenting npm publish on any pull request. All ten malicious versions carry valid npm provenance attestations, so npm audit signatures will not flag them.

Bumblebee scan-time exposure check: exact (ecosystem, package, version) presence match against on-disk manifests / lockfiles. Not intended to check network/file/process IOCs.