The reviewed flows are consistent with Bkper CLI authentication, AI provider integrations, AWS Bedrock credential resolution, and version checking. The flagged behaviors do not show credential theft or unrelated data exfiltration.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
CLI use; provider credential flows when the relevant AI provider is used.
Impact
No evidence that credentials or unrelated data are sent to an attacker-controlled destination, or that package code runs during installation.
Mechanism
Stored Bkper credentials go to the Bkper platform; Kimi login uses Kimi OAuth; the AWS SDK metadata provider supplies credentials for Bedrock. CLI startup checks the npm registry for updates.
Evidence
package.jsonlib/cli.jslib/commands/context/platform-context.jslib/agent/bundle/kimi-coding.jslib/agent/bundle/bedrock-converse-stream.jslib/upgrade/installation.js
Network endpoints5
platform.bkper.appauth.kimi.com