@lyra_wang/chrome-frequent-pages@0.5.3
Chrome 高频网页 → 飞书「常用网页」表 + 按分类导出 Chrome 书签（根域名 / 10 天 / >5 次）
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe optional scheduled feature uses the user's Lark credentials to write to a fixed Feishu inbox chosen by the package, and its summary can carry page titles and domains. The documented opt-in does not let the user choose that destination, so this is an unauthorized account action with potential data disclosure.
Static reason
No blocking static signals were detected.
Trigger
The user runs install.sh; launchd then runs the job at load and it runs at most weekly.
Impact
The user's authenticated account performs a write to a publisher-selected Feishu destination, potentially exposing page details in the submitted summary.
Mechanism
The job snapshots a fixed Feishu table, runs the collector in write mode, builds a title/domain summary, and submits it through lark-cli --as user to a hard-coded inbox.
Attack narrative
After the user runs the optional installer, launchd triggers a weekly job. It runs the collector in write mode, constructs a summary that can include page titles and domains, then uses the user's Lark identity to create a record in an inbox identified by hard-coded Feishu base and table IDs. The inbox destination is not selected through the package configuration.
AI rationale
The optional scheduled feature uses the user's Lark credentials to write to a fixed Feishu inbox chosen by the package, and its summary can carry page titles and domains. The documented opt-in does not let the user choose that destination, so this is an unauthorized account action with potential data disclosure.
Evidence
install.shrun-if-due.shinbox-deliver-mac.pytable_snapshot.py~/Library/LaunchAgents/com.lyrawang.chrome-frequent-pages.plist~/.config/chrome-frequent-pages/last-run.json~/.config/chrome-frequent-pages/run-if-due.log
Decision evidence
public snapshotAI called this Malicious at 91.0% confidence as Malware with low false-positive risk.
Evidence for block
- The optional installer registers run-if-due.sh as a launchd job that runs at load.
- The scheduled script runs chrome-frequent-pages --write and takes snapshots around the run.
- The inbox helper hard-codes a Feishu base and inbox table.
- The helper invokes lark-cli with --as user, so the action uses the user's identity.
- The generated summary can contain page titles and domains from the snapshot diff.
- The helper creates a record in the hard-coded inbox with that summary.
Evidence against
- The recurring job requires the user to run install.sh; the README describes the weekly run and inbox delivery.
- The npm manifest has no lifecycle scripts, so npm installation alone does not start the scheduled behavior.
Behavioral surface
ChildProcess
Source & flagged code
7 flaggedinbox-deliver-mac.pyView file
11BASE = "NeujbbOfcaPEvMsPIxscaJImn9d"
INBOX = "tbl9LghPBTjFLH4N"
TASKS = "tbl4k7ggY1paqoUn"
LARK = "lark-cli"
def lark(args):
cmd = [LARK] + args + ["--as", "user", "--format",
High
Ai Review Evidence
The inbox helper hard-codes a Feishu base and inbox table.
inbox-deliver-mac.pyView on unpkg · L1116def lark(args):
cmd = [LARK] + args + ["--as", "user", "--format", "json"]
res = subprocess.run(cmd, capture_output=True, text=True,
High
Ai Review Evidence
The helper invokes lark-cli with --as user, so the action uses the user's identity.
inbox-deliver-mac.pyView on unpkg · L1658rid = task_record_id(args.task)
if rid:
record["关联任务"] = [rid]
lark(["base", "+record-batch-create", "--base-token", BASE, "--table-id", INBOX,
"--json"
High
Ai Review Evidence
The helper creates a record in the hard-coded inbox with that summary.
inbox-deliver-mac.pyView on unpkg · L58Findings
6 High1 Medium
HighAi Review Evidenceinstall.sh
HighAi Review Evidencerun-if-due.sh
HighAi Review Evidenceinbox-deliver-mac.py
HighAi Review Evidenceinbox-deliver-mac.py
HighAi Review Evidencerun-if-due.sh
HighAi Review Evidenceinbox-deliver-mac.py
MediumShips Build Helperinbox-deliver-mac.py
Affected versions and remediation
This report applies to @lyra_wang/chrome-frequent-pages@0.5.3.
See all versions of @lyra_wang/chrome-frequent-pages for other recorded verdicts.
- Avoid installing @lyra_wang/chrome-frequent-pages@0.5.3. 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.