# Trust Granted at Admission Must Be Re-Verified at Every Update ## Claim A distribution channel that reviews participants once at entry and then ships their subsequent changes unexamined has an open supply-chain path, because compromise happens after trust is established rather than before it. <!-- atomicity: 1 idea ✓ --> ## Scope & conditions - Applies to any channel where admission and distribution are separate events: package registries, plugin and extension directories, app stores, and contributor commit access. - The gap widens with time since admission and with how many hands hold publishing rights — an account compromise years after review inherits the original trust. - Re-verification must key off the artifact that actually ships. A gate triggered by tagged releases does not cover code introduced by other routes. - Distinct from signing: signatures prove who published, not whether what they published is safe. ## Evidence Announcing automated security review for WordPress.org plugin releases, Plugins Team co-rep David Pérez named the gap directly — *"A plugin can be secure today and introduce a vulnerability, or malicious code, in a future release"* — and said that until now *"there was no consistent review step between a release being committed and that release reaching millions of sites."* Every release is now analyzed during a cooldown window by multiple AI models alongside Jetpack Scan, with high-risk releases blocked before reaching the update API. The July ARVE backdoor (~20,000 installs) was caught inside that window and never distributed. ## Caveat on coverage The described trigger is a release event. Austin Ginder separately documented malware sitting in the *trunk* of a 40,000-install plugin (instawp-connect) where the stable zip never moved — a compromise that would not have been a release, and therefore may fall outside this gate. Two different incidents; the trunk vector remains an open question rather than a demonstrated gap. ## Links - [[3. Resources/Permanent Notes/A Timed Review Window Trades Update Speed for Supply-Chain Safety]] — because extends; that note analyses the cost of the delay, this one explains why a delay is needed at the update boundary specifically rather than at admission. - [[3. Resources/Permanent Notes/Update Signatures Prove Provenance Not Freshness]] — because extends; signatures answer "who shipped this" and leave "is it safe" to a review step this claim argues must exist. - [[3. Resources/Permanent Notes/A Single Discretionary Update Channel Is a Security Dependency]] — because applies-in; if the channel is a dependency, re-verification at each use is the control that makes it a safer one. - [[3. Resources/Permanent Notes/Automated Review Is Only As Accountable As The Standards Behind It]] — because contrasts; re-verification is necessary but inherits the accountability problem of whatever standard does the verifying. - [[3. Resources/MOCs/WordPress Hosting Security Stack MOC]] — because applies-in; the update API became a policy enforcement point, not just a distribution endpoint. - [[3. Resources/MOCs/Open Source Governance MOC]] — because applies-in; who reviews what, and at which point in the release path, is a governance decision about the distribution channel and not only a security control. ## Tests / falsifiers - Compare counts of malicious code caught at admission versus at update across a registry over a fixed window. If admission review catches the majority, the claim's premise about timing is wrong. - Commit a readme-only change to a plugin under your own control and observe whether a scan and cooldown trigger. This settles whether the gate keys off releases or off commits. - Check whether ecosystems without an update-boundary gate (npm, PyPI, Packagist) show higher rates of post-admission compromise, controlling for package volume. ## Maintenance - Last tended: 2026-09-10 - Next review: 2026-12-10 ## Source - [[3. Resources/Readwise/Articles/WordPress.org Can Now Automatically Block High-Risk Plugin Updates Before They Ship]] — The Repository's coverage of the Pérez announcement, including the ARVE disclosure. - [Grok Bot Found Malware on WP.org During a Routine Check.](3.%20Resources/Readwise/Articles/Grok%20Bot%20Found%20Malware%20on%20WP.org%20During%20a%20Routine%20Check..md) — Austin Ginder's independent trunk-level find, the source of the coverage caveat above.