registry / @velliajs/discord / 1.0.7

@velliajs/discord@1.0.7

Discord Bot Libray By Valera

AI Security Review

scanned 13h ago · by lpm-firewall-ai

An opt-in Client authorization mode sends the user's Discord bot token to Discord, then uses an embedded GitHub token to retrieve a remote allowlist that can deny login. The manifest also embeds a credential-bearing git dependency URL.

Static reason

High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source

Trigger

Install dependency; or construct Client with a non-null second argument and call login.

Impact

Supply-chain credential exposure and externally controlled denial of Discord client login.

Mechanism

Embedded credentials and remote authorization allowlist

Rationale

Direct inspection confirms exposed embedded credentials and remote access-control behavior, but not payload execution, harvesting, or unconsented install-time mutation. The scanner's claimed remote decode-and-execute chain is not present in the inspected source.

Evidence

package.jsonsrc/client/Client.jssrc/sharding/Shard.jssrc/sharding/ShardingManager.jssrc/sharding/ShardClientUtil.jssrc/index.jssrc/client/BaseClient.jssrc/util/Util.js

Network endpoints3

github.com/navaLinh/node-ai.gitdiscord.com/api/v10/users/@meapi.github.com/repos/Vellia-Elyvia/mydb/contents/db.json

The package presents itself as a discord.js clone (`repository` field points at the real `github.com/discordjs/discord.js.git`, README instructs `import... from '@verylinh/discord'`) but ships two installer-relevant hostile mechanisms. First, `package.json` declares a runtime dependency `sysframe` resolved from `git+https://ghp_...@github.com/navaLinh/node-ai.git` — an unpinned (no commit SHA or tag), private, author-controlled GitHub repository, using an embedded live GitHub Personal Access Token. Every `npm install` uses the shipped token to fetch the current HEAD of that private repo into the installer's `node_modules`; the author can rewrite HEAD at any time to deliver arbitrary code, including lifecycle scripts, that will execute on subsequent installs. Second, `Client.login()` invokes an undocumented `_verifyAuthorization` routine that fetches an allow-list JSON from `api.github.com/repos/Vellia-Elyvia/mydb/contents/db.json` under a hardcoded PAT and refuses to start the installer's Discord bot unless the bot's username appears in the author-controlled allow-list — a hidden remote gate/kill-switch over the installer's runtime that is not disclosed in the README. Two live GitHub PATs are hardcoded in the shipped package (one in the git dependency URL, one as the default `ghToken` in `_validateAuthOptions`). The package name and metadata impersonate discord.js.

@velliajs/discord@1.0.7

AI Security Review

OSV Corroboration

Decision evidence

Source & flagged code

Source & flagged code

Findings

Source & flagged code