critical
suspicious.env_credential_access
- Location
- assets/dashboard-api-starter/src/auth.ts:7
- Finding
- Environment variable access combined with network send.
HypDiscordGOD
AdvisoryAudited by Static analysis on May 10, 2026.
Overview
Detected: suspicious.env_credential_access
Findings (2)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
What this means
If this starter is run on a reachable network, unauthorized callers could create or alter moderation records and audit entries, which could mislead staff or downstream automation.
Why it was flagged
The moderation dashboard starter exposes routes that write warning, moderation-action, and audit-log records without visible authentication, guild permission checks, CSRF checks, or route-level authorization.
Skill content
app.use(cors()); ... app.post('/warnings', (req, res) => { ... INSERT INTO warnings ... }); ... app.post('/mod-actions', (req, res) => { ... INSERT INTO mod_actions ... });Recommendation
Before using this beyond local experimentation, add dashboard authentication, per-guild Manage Guild or moderator checks, CSRF protection for browser flows, input validation, and restrictive CORS.
What this means
A leaked or over-permissioned bot token could let someone control the bot in your Discord servers.
Why it was flagged
The scaffolded bot logs into Discord with a bot token. This is necessary for the skill's stated purpose, but it grants whatever Discord permissions the user assigns to that bot.
Skill content
await client.login(process.env.DISCORD_TOKEN);
Recommendation
Use least-privilege bot permissions and intents, store tokens only in protected environment variables or secret managers, and rotate tokens if exposed.
What this means
If the API process or memory is compromised while sessions are active, OAuth tokens could be abused to access Discord identity and guild-list information.
Why it was flagged
The dashboard API starter stores Discord OAuth access and optional refresh tokens in an in-memory session map. This is disclosed as development-grade in the skill guidance, but the data is sensitive.
Skill content
accessToken: string; refreshToken?: string; ... sessions.set(sessionId, { discordUserId, accessToken, refreshToken, ... expiresAt ... });Recommendation
For production, use HTTPS, secure cookies, a hardened server-side session store, careful refresh-token handling, session expiration, and logout/rotation behavior.
What this means
Private Discord ticket conversations may remain on disk after a ticket is closed.
Why it was flagged
The ticket bot starter exports recent ticket-channel messages and attachment URLs to local transcript files. This is purpose-aligned and disclosed, but ticket transcripts can contain private support content.
Skill content
const messages = await channel.messages.fetch({ limit: 100 }); ... fs.writeFileSync(filePath, transcript || '[empty transcript]\n', 'utf8');Recommendation
Set a clear transcript retention policy, restrict filesystem access, avoid storing unnecessary sensitive content, and tell server members how transcripts are handled.
Findings (2)
critical
suspicious.env_credential_access
- Location
- assets/ticket-bot-starter/src/index.ts:36
- Finding
- Environment variable access combined with network send.