The default first-message path can install and execute a newer release of the publisher’s companion package globally, with no advance disclosure; the opt-out is not documented in the package README. This is a concrete, automatic update capability, so block as remote code execution with dangerous-capability intent.
Static reason
No blocking static signals were detected.
Trigger
The first chat.message event after the plugin starts, when a globally installed xp-gate package is older than the npm latest version and autoUpgrade is not disabled in ~/.xp-gate/config.json.
Mechanism
The plugin checks the npm registry and runs npm install -g @boyingliu01/xp-gate@<latest-version>. It announces the update only after installation.
Attack narrative
On the plugin’s first chat.message event, it checks the npm registry for the latest @boyingliu01/xp-gate version. If the globally installed companion is outdated, the plugin runs npm install -g for that version. The autoUpgrade: false setting can disable the update, but the package documentation does not describe this behavior and the notice is emitted only after installation. This exposes users to automatic execution of newly published package code without advance notice.
Evidence
index.tspackage.json~/.xp-gate/xp-gate-version-check.json~/.xp-gate/config.json~/.xp-gate/upgrade-notice.json