registry / @luoyi-dsh/discord-plugin / 1.0.4
@luoyi-dsh/discord-plugin@1.0.4
DeepSeek Harness (DSH) Discord 用戶帳號 (Selfbot) 助理與 MCP 插件：支援自然穿插閒聊、被提及與私訊智慧代回、傳送文字、圖片、文件與貼圖
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe flagged LLM code uses credentials for requests to their configured or corresponding provider services, and the prepare script only builds the package. The automatic Discord messaging features match the package’s stated purpose and are controlled through its configuration.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
LLM requests occur when configured Discord reply or co-chat features need a response, or when a user tests the configured LLM connection.
Impact
No unrelated credential transfer or other malicious behavior was found in the inspected paths.
Mechanism
The plugin sends provider credentials with requests to the matching provider endpoint. Google OAuth refresh uses Google’s token endpoint.
AI rationale
The flagged LLM code uses credentials for requests to their configured or corresponding provider services, and the prepare script only builds the package. The automatic Discord messaging features match the package’s stated purpose and are controlled through its configuration.
Evidence
~/.dsh/plugins/subscriptions/auth.jsondata/config.jsondata/ledger.json
Network endpoints5
oauth2.googleapis.comdaily-cloudcode-pa.googleapis.comcloudcode-pa.googleapis.comapi.x.aiapi.deepseek.com
Decision evidence
public snapshotAI called this Clean at 87.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The only lifecycle script is prepare, which runs the TypeScript build.
- LLM API keys are resolved from plugin configuration, provider-specific environment variables, or DSH credentials.
- Google OAuth refresh tokens are sent to Google’s OAuth endpoint; subscription access tokens go to Google’s Cloud Code endpoints.
- Custom API keys are sent as bearer credentials to the configured API base, defaulting to api.deepseek.com.
- The package entrypoint loads configuration and creates a Discord client; login requires a configured user token and autoStart.
- Discord replies and autonomous chat are advertised package features, with controls and limits in configuration.
Evidence against
- The LLM code reads API keys from environment variables and a local credentials file, and reads subscription tokens from local auth.json.
- Default settings enable mention replies, DM replies, and autonomous co-chat when a Discord token is configured.
Behavioral surface
CryptoDynamicRequireEnvironmentVars
Source & flagged code
4 flaggedclient.jsView file
18factory: (require) => {
L19: const React = require('react')
L20: const h = React.createElement
Medium
Dynamic Require
Package source references dynamic require/import behavior.
client.jsView on unpkg · L18dist/lib/llm.jsView file
17try {
L18: const home = process.env.DSH_HOME || join(process.env.USERPROFILE || process.env.HOME || '', '.dsh');
L19: const authPath = join(home, 'plugins', 'subscriptions', 'auth.json');
L20: if (existsSync(authPath)) {
L21: const data = JSON.parse(readFileSync(authPath, 'utf-8'));
L22: const list = [];
...
L126: try {
L127: const tokenResp = await fetch('https://oauth2.googleapis.com/token', {
L128: method: 'POST',
L129: headers: { 'content-type': 'application/x-www-form-urlencoded' },
L130: body: new URLSearchParams({
L131: client_id: oauthClientId,
Critical
Credential Exfiltration
Source appears to send environment or credential material to an external endpoint.
dist/lib/llm.jsView on unpkg · L1717
Findings
2 Critical1 High4 Medium5 Low
CriticalCredential Exfiltrationdist/lib/llm.js
CriticalTrigger Reachable Dangerous Capabilitydist/lib/llm.js
HighTrigger Reachable Credential Exfiltrationdist/lib/llm.js
MediumDynamic Requireclient.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @luoyi-dsh/discord-plugin@1.0.4.
See all versions of @luoyi-dsh/discord-plugin for other recorded verdicts.
- Review the evidence and your use of @luoyi-dsh/discord-plugin@1.0.4 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.