registry / @yoooclaw/phone-notifications / 1.20.1
@yoooclaw/phone-notifications@1.20.1
后台同步手机通知数据到本地存储，供 Agent 查询消费
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe manifest and inspected code indicate a phone-notification plugin with a CLI and update support. The scanner’s credential and subprocess leads resolve to package-service authentication, update reporting, and an updater launched for a prepared update; no unrelated credential exfiltration or malicious default action was established.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Plugin import, user-invoked CLI commands, and update operations initiated through the plugin.
Impact
No malicious impact identified from the reviewed source.
Mechanism
The inspected credential use supports the package’s own service and update reporting; the updater runs only after a prepared update is started.
AI rationale
The manifest and inspected code indicate a phone-notification plugin with a CLI and update support. The scanner’s credential and subprocess leads resolve to package-service authentication, update reporting, and an updater launched for a prepared update; no unrelated credential exfiltration or malicious default action was established.
Network endpoints1
artifact.yoooclaw.com
Decision evidence
public snapshotAI called this Clean at 89.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exposes a plugin entrypoint and CLI; its only install-adjacent lifecycle script is the build-only prepublishOnly hook.
- Provisioning uses a link-secret flow and stores the exchanged API key in the package credentials file; existing keys without a link secret are left unchanged.
- Update reporting reads this package’s credentials and sends the key with update events to the configured report endpoint.
- Update download and detached updater behavior are part of the explicit update flow.
Evidence against
- The reported npm credential matches are broad scanner leads; the inspected report code uses the package’s own API key for update reporting.
- The automatic updater is not invoked by the detached updater helper itself; it requires a prepared update status.
- No unrelated credential collection, install-time data transmission, or reviewer-directed manipulation was identified.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEval
Source & flagged code
13 flaggeddist/bin/ntf.cjsView file
67class CommanderError extends Error {
L68: constructor(exitCode, code, message) {
L69: super(message);
...
L785: var EventEmitter = require("node:events").EventEmitter;
L786: var childProcess = require("node:child_process");
L787: var path = require("node:path");
...
L831: this._outputConfiguration = {
L832: writeOut: (str) => process2.stdout.write(str),
L833: writeErr: (str) => process2.stderr.write(str),
...
L2287: for (let i = 0;i < namespace.length; i++) {
L2288: hash = (hash << 5) - hash + namespace.charCodeAt(i);
L2289: hash |= 0;
Critical
Credential Exfiltration
Source appears to send environment or credential material to an external endpoint.
dist/bin/ntf.cjsView on unpkg · L67785var EventEmitter = require("node:events").EventEmitter;
L786: var childProcess = require("node:child_process");
L787: var path = require("node:path");
High
1245}
L1246: const execArgv = process2.execArgv ?? [];
L1247: if (execArgv.includes("-e") || execArgv.includes("--eval") || execArgv.includes("-p") || execArgv.includes("--print")) {
Findings
2 Critical8 High5 Medium7 Low
CriticalCredential Exfiltrationdist/bin/ntf.cjs
CriticalTrigger Reachable Dangerous Capabilitydist/index.cjs
HighChild Processdist/bin/ntf.cjs
HighShelldist/bin/ntf.cjs
HighCredential Redirect Persistencedist/index.cjs
HighCommand Output Exfiltrationdist/bin/ntf.cjs
HighHidden Inline Dependency Executiondist/bin/ntf.cjs
HighCross File Remote Execution Contextdist/index.cjs
HighTrigger Reachable Credential Exfiltrationdist/index.cjs
HighSemantic Analysis Limiteddist/index.cjs
MediumDynamic Requiredist/bin/ntf.cjs
MediumNetwork
Affected versions and remediation
This report applies to @yoooclaw/phone-notifications@1.20.1.
See all versions of @yoooclaw/phone-notifications for other recorded verdicts.
- Review the evidence and your use of @yoooclaw/phone-notifications@1.20.1 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.