dokugen@14.2.2
Readme generator command line tool.
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe source shows GitHub credentials being forwarded to the publisher-selected Dokugen backend during normal authenticated command use, without recipient-specific consent. This is concrete credential disclosure and warrants blocking publication.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
After GitHub login, a user invokes an authenticated command such as README or changelog generation.
Impact
The backend receives a GitHub credential with read and offline access scopes, exposing the associated account credential to a recipient other than GitHub.
Mechanism
The shared request helper places the stored GitHub token in the Authorization bearer header for requests to the Dokugen backend.
Attack narrative
The device login flow obtains and stores a GitHub access token. Authenticated commands then use a shared helper that sends that token as a bearer credential to the Dokugen backend, whose default host is publisher-selected. The source does not establish recipient-specific consent to disclose the GitHub token to that backend.
AI rationale
The source shows GitHub credentials being forwarded to the publisher-selected Dokugen backend during normal authenticated command use, without recipient-specific consent. This is concrete credential disclosure and warrants blocking publication.
Evidence
dist/bin/helpers/auth.mjsdist/bin/helpers/network.mjsdist/bin/helpers/readme.mjsdist/bin/commands/changelog.mjs
Network endpoints2
github.com/login/device/codedokugen.samueltuoyo.com
Decision evidence
public snapshotAI called this Malicious at 97.0% confidence as Malware with low false-positive risk.
Evidence for block
- The login flow requests GitHub access with read, email, and offline access scopes, then stores the returned access token.
- The request helper adds the stored GitHub access token as a bearer credential to authenticated requests.
- The default backend is dokugen.samueltuoyo.com, and README generation sends an authenticated request there.
- The changelog command authenticates before sending an authenticated request to the backend.
Evidence against
- The postinstall script only attempts to set an executable permission on a local path.
- The authenticated requests occur through user-invoked application commands.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
6 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node -e "import('fs').then(fs => { if (fs.existsSync('dist/scripts/postinstall.mjs')) import('./dist/scripts/postinstall.mjs'); }).catch(() => {})"
Critical
Red Install Lifecycle Script
Install-time lifecycle script matches a deterministic static-gate block pattern.
package.jsonView on unpkg•scripts.postinstall = node -e "import('fs').then(fs => { if (fs.existsSync('dist/scripts/postinstall.mjs')) import('./dist/scripts/postinstall.mjs'); }).catch(() => {})"
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkgdist/bin/commands/changelog.mjsView file
1import { execFileSync, execSync } from "node:child_process";
L2: import path from "node:path";
High
Child Process
Package source references child process execution.
dist/bin/commands/changelog.mjsFindings
2 Critical4 High3 Medium5 Low
CriticalRed Install Lifecycle Scriptpackage.json
CriticalPrevious Version Dangerous Deltadist/bin/helpers/auth.mjs
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processdist/bin/commands/changelog.mjs
HighShell
HighSame File Env Network Executiondist/bin/helpers/readme.mjs
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowWeak Cryptodist/bin/helpers/fileOps.mjs
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to dokugen@14.2.2.
See all versions of dokugen for other recorded verdicts.
- Avoid installing dokugen@14.2.2. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.