registry / Data exfiltration / blogger-publisher
blogger-publisher
A powerful CLI to automate your Blogger publishing using Markdown, Multi-CDN, and AI Agents.
This report shows the evidence for blogger-publisher@1.3.2. 1 of 4 known versions is blocked or flagged. The newest version, 1.3.4, is allowed. See all versions.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiBundled operational OAuth credentials create a concrete, implicit data-routing path from user files to a third-party account. The absence of install hooks does not mitigate this user-triggered exfiltration behavior.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Running `blogger-publisher publish` without overriding the bundled configuration.
Impact
User content and images can be uploaded to a third-party account; Drive uploads are made public.
Mechanism
Packaged OAuth credential injection into publishing and image-upload flows.
Attack narrative
The package ships an OAuth refresh token and default blog configuration, then loads them implicitly through `dotenv`. When a user runs the documented publishing flow without replacing configuration, local Markdown and referenced images are sent using the embedded account; the Drive uploader also grants public read access to uploaded images.
AI rationale
Bundled operational OAuth credentials create a concrete, implicit data-routing path from user files to a third-party account. The absence of install hooks does not mitigate this user-triggered exfiltration behavior.
Evidence
.envlib/config.jslib/auth.jslib/publisher.jslib/uploaders/drive.jspackage.json
Network endpoints2
www.googleapis.com/auth/bloggerwww.googleapis.com/auth/drive.file
Decision evidence
public snapshotAI called this Malicious at 91.0% confidence as Malware with low false-positive risk.
Evidence for block
- `.env` embeds a Google OAuth client secret and refresh token with a default `BLOG_ID`.
- `lib/config.js` automatically loads packaged `.env` values when no user config exists.
- `lib/publisher.js` reads user-selected Markdown and publishes it through the authenticated Blogger client.
- `lib/uploaders/drive.js` uploads local images using that OAuth client and makes them publicly readable.
Evidence against
- `package.json` has no `preinstall`, `install`, or `postinstall` hook.
- `lib/updater.js` only self-updates after an interactive confirmation and targets its own package.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
5 flagged · loading source.envView file
1patternName = blocked_file
severity = critical
matchedText = .env
redactedSecretContext =
secretLikeLines = 4
L1: BLOG_ID=<redacted:19 hex>
L2: CLIENT_ID=<redacted:72 token-like>
L3: CLIENT_SECRET=<redacted:35 token-like>
L6: REFRESH_TOKEN=<redacted:103 token-like>
Critical
lib/updater.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = blogger-publisher@1.3.0
matchedIdentity = npm:YmxvZ2dlci1wdWJsaXNoZXI:1.3.0
similarity = 0.400
summary = stored previous version shares package body but lacks this dangerous source file
Critical
Previous Version Dangerous Delta
This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
lib/updater.jsView on unpkg3const p = require('@clack/prompts');
L4: const { execSync } = require('child_process');
L5: const pkg = require('../package.json');
High
Findings
2 Critical3 High3 Medium5 Low
CriticalCritical Secret.env
CriticalPrevious Version Dangerous Deltalib/updater.js
HighChild Processlib/updater.js
HighShell
HighRuntime Package Installlib/updater.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowWeak Cryptolib/uploaders/github.js
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to blogger-publisher@1.3.2.
The versions list below shows the verdict for each recorded version.
- Avoid installing blogger-publisher@1.3.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.