The flagged subprocess and credential references are consistent with a desktop host that launches agent sessions and embeds CLI code; I did not establish credential theft or an unrelated download-and-execute path. The host does, however, apply Centralu updates from npm automatically on the default app path, and the package snapshot does not establish pre-run disclosure, so warn about this self-update capability.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
Host startup when Centralu is launched as an app or by its keeper, with automatic updates enabled by default for those builds.
Impact
A newer vendor package can be installed without a separate user request. The reviewed source does not establish that the update payload is malicious, but pre-run disclosure of this default is not established in the package snapshot.
Mechanism
The host checks for a newer release and can run npm install for that Centralu version, then refresh the installed app copy.
Evidence
Centralu.app/Contents/Resources/content/host/main.mjs