registry / @taole/dd-playwright / 0.1.12
@taole/dd-playwright@0.1.12
Standalone stdio MCP & CLI: Playwright browser automation + isolated whistle proxy + diandian account storageState injection
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe web console exposes stored account cookies through an unauthenticated endpoint while binding to 0.0.0.0. This is a serious credential disclosure vulnerability, although the source does not show the package itself sending those credentials to an attacker.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review; previous stored version diff introduced dangerous source
Trigger
A user starts the web console with serve or startweb; it listens on all interfaces by default.
Impact
A reachable network client can read reusable account session cookies and access the corresponding Diandian accounts.
Mechanism
GET /api/accounts returns account data including cookieHeader, with no authentication, and JSON responses allow any origin.
AI rationale
The web console exposes stored account cookies through an unauthenticated endpoint while binding to 0.0.0.0. This is a serious credential disclosure vulnerability, although the source does not show the package itself sending those credentials to an attacker.
Evidence
src/server/web-server.mjssrc/account-store.mjsbin/cli.mjs
Network endpoints2
0.0.0.0:<port> (default port 12309)/api/accounts
Decision evidence
public snapshotAI called this Suspicious at 99.0% confidence as Critical Vulnerability with medium false-positive risk.
Evidence for warning
- The web console listens on 0.0.0.0, making it reachable through any interface where network controls allow access.
- The unauthenticated GET /api/accounts handler returns account records and the active account.
- Account records include the stored cookieHeader, exposing reusable account session credentials.
- The JSON response sets Access-Control-Allow-Origin: *, allowing cross-origin reads of the unauthenticated endpoint.
Evidence against
- The package has no install, preinstall, or postinstall lifecycle scripts.
- The updater runs npm install only when the user invokes the update command.
- The login flow verifies cookies against the Diandian API that issued them.
Behavioral surface
ChildProcessEnvironmentVarsEvalFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
4 flaggedsrc/updater.mjsView file
2import { fileURLToPath } from "node:url";
L3: import { execSync } from "node:child_process";
L4: import { resolveConfig } from "./config.mjs";
High
115try {
L116: execSync(`npm install -g ${PACKAGE_NAME}@latest`, {
L117: stdio: "inherit",
High
Runtime Package Install
Package source invokes a package manager install command at runtime.
src/updater.mjsView on unpkg · L115src/server/daemon.mjsView file
•matchType = normalized_sha256
matchedPackage = @taole/dd-playwright@0.1.6
matchedPath = src/server/daemon.mjs
matchedIdentity = npm:QHRhb2xlL2RkLXBsYXl3cmlnaHQ:0.1.6
similarity = 1.000
summary = normalized source hash matched finalized malicious source
High
Findings
1 Critical4 High3 Medium5 Low
CriticalPrevious Version Dangerous Deltasrc/browser-manager.mjs
HighChild Processsrc/updater.mjs
HighShell
HighRuntime Package Installsrc/updater.mjs
HighKnown Malware Source Similaritysrc/server/daemon.mjs
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowEval
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @taole/dd-playwright@0.1.12.
See all versions of @taole/dd-playwright for other recorded verdicts.
- Review the evidence and your use of @taole/dd-playwright@0.1.12 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.