Socket found ten malicious releases of @7nohe/openapi-react-query-codegen on August 28, 2026, published in two waves and still installable at the time of writing. The latest tag still resolves to version 3.0.4, so the package name and release lineage look normal even though the build is compromised.
Socket says the attacker abused a comment-triggered GitHub Actions publishing workflow, which let an untrusted GitHub account publish code under the repository’s trusted identity. That matters because the releases carry valid npm provenance attestations while still running threat-actor-controlled code during install, with payloads aimed at cloud credentials, registry tokens, GitHub Actions secrets, and AI-agent settings.
The exposure sits in the publishing path, not just in one package version: if your tooling treats provenance as a hard safety check, this case shows that the trust mark can be genuine while the code it authenticates is malicious. Teams that consume npm packages through GitHub Actions trusted publishing or automated dependency updates inherit that risk until the release source itself is trusted.