The install hook and login startup perform documented setup and maintenance for the package’s Microsoft 365 gateway. The inspected update path verifies downloaded archives, and I found no unrelated credential exfiltration or account actions.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review; previous stored version diff introduced dangerous source
Trigger
A global nonportable npm install on Windows runs setup; the configured current-user login startup entry later checks for updates and starts the gateway.
Impact
The disclosed behavior installs and maintains the gateway and its login startup entry; inspected source showed no unrelated credential transfer or external account action.
Mechanism
The updater contacts the package’s configured distribution host, verifies downloaded archives, and activates the runtime. Setup writes the package’s own startup entry.
Evidence
scripts/postinstall.mjsscripts/package-install.mjsscripts/startup-update.mjsscripts/runtime-update.mjsscripts/Configure-ApiStartup.ps1%APPDATA%\Microsoft\Windows\Start Menu\Programs\Startup\m365-api.vbs