@yoooclaw/phone-notifications@1.19.1
后台同步手机通知数据到本地存储，供 Agent 查询消费
AI Security Review
scanned 15d ago · by lpm-firewall-aiThe package does not declare an npm install hook; its prepublishOnly hook builds the package. Runtime notification sending can expose the saved API key when a custom endpoint is configured, so a warning is warranted without evidence of a covert default export.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A user or agent invokes the light control tool while a custom notification URL is configured.
Impact
The configured recipient can receive the API key; source review found no hidden default export.
Mechanism
The package accepts the configured URL and includes the saved API key in the request header.
AI rationale
The package does not declare an npm install hook; its prepublishOnly hook builds the package. Runtime notification sending can expose the saved API key when a custom endpoint is configured, so a warning is warranted without evidence of a covert default export.
Evidence
dist/index.cjs
Network endpoints2
openclaw-service.yoooclaw.comNOTIFICATION_INTELLIGENCE_LIGHT_EFFECTS_SEND_URL
Decision evidence
public snapshotAI called this Suspicious at 91.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The manifest's only lifecycle hook is prepublishOnly, which runs a build.
- The API key is loaded from YOOOCLAW_API_KEY or saved credentials.
- Production uses a YoooClaw host by default, but an environment variable can replace the notification destination.
- URL normalization preserves supplied destinations without restricting their host.
- The notification request sends the API key in the X-Api-Key-Id header.
- Invoking the light control tool calls the sender with the loaded API key.
Evidence against
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetworkShell
HighEntropyStringsUrlStrings
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.19.1.
See all versions of @yoooclaw/phone-notifications for other recorded verdicts.
- Review the evidence and your use of @yoooclaw/phone-notifications@1.19.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.