Topic starter
19/08/2026 3:34 pm
TL;DR: A 14 July 2026 compromise of the AsyncAPI ecosystem turned GitHub Actions release automation into malicious trusted publishing after attackers abused a pull_request_target workflow, a stolen privileged token, and legitimate provenance to ship five poisoned package versions, according to Corgea. The incident shows that CI trust boundaries, not just npm token hygiene, now define supply-chain exposure.
Editorial analysis by NHI Mgmt Group, based on content published by Corgea: “AsyncAPI's July 14 npm compromise chained `pull_request_target`, unsigned branch pushes, and require-time malware”.
Key questions
Q: What breaks when pull_request_target is used to run untrusted code in GitHub Actions?
A: The base repository’s privilege model breaks.
Q: Why do GitHub Actions release tokens and bot accounts need NHI governance?
A: Because they are delegated non-human identities with real publishing power.
Q: What do security teams get wrong about provenance in software delivery?
A: They often treat provenance as documentation rather than a continuously verifiable control.
Practitioner guidance
- Split untrusted PR validation from privileged release paths Keep pull_request_target jobs free of checkout-and-execute patterns, and move build or test execution for forked code into an unprivileged pipeline that cannot access secrets or publish artifacts.
- Inventory CI principals as non-human identities Map GitHub bots, release tokens, and signing credentials to owners, scopes, and expiry dates so release authority is visible alongside human account access.
- Audit package imports for top-level execution Search for modules that run code at require() time, especially in generator, parser, and schema-validation dependencies that are imported in CI or developer tooling.
Bottom line: The incident exposes a CI trust-boundary problem, not just a package-hygiene problem, because the attacker used privileged workflow execution to publish malicious packages.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
19/08/2026 4:15 pm
CI trust-boundary failure is now a release-security problem, not just a workflow hygiene issue. The AsyncAPI compromise shows that a privileged workflow can become the delivery mechanism for malicious artifacts when untrusted code is allowed to cross into release authority. That shifts governance from simple token hygiene to control over where code is allowed to execute and what authority the job holds at that moment. Practitioners should treat release automation as an access-control surface, not only a build system.
A question worth separating out:
Q: Should teams prioritise CI/CD access governance or package scanning first?
A: Teams should not treat them as separate choices. Package scanning finds risky components, but CI/CD access governance determines who can introduce or approve them. In a high-velocity pipeline, governance over build identities and promotion rights is the control that keeps scanning findings from becoming live exposure.
👉 Read our full editorial: AsyncAPI supply chain compromise exposed CI trust-boundary failures