diggylab-worker@0.1.35
DiggyLab Desktop Agent collects posts and information from Facebook Groups on a paired computer. (self-hosted scan worker)
AI Security Review
scanned 8d ago · by lpm-firewall-aiThe user-invoked login path discloses Facebook session credentials to the package-default API without recipient-specific consent. The postinstall browser setup is benign but does not change this runtime credential transfer.
Static reason
One or more suspicious static signals were detected.
Trigger
A user invokes the login command and completes Facebook browser login or supplies Facebook cookies.
Impact
The API receives reusable Facebook session credentials, which could enable access to the associated account.
Mechanism
The worker packages the Facebook session state and posts it to the API session endpoint. The default recipient is package-selected, and the source does not obtain recipient-specific consent before sending.
Attack narrative
When login completes, the worker sends the Facebook session to its API. The default API host is selected by the package, while the login flow does not ask the user to approve sending Facebook credentials to that recipient. Invoking Facebook login establishes consent to authenticate, not consent to disclose the session to the package-selected API.
AI rationale
The user-invoked login path discloses Facebook session credentials to the package-default API without recipient-specific consent. The postinstall browser setup is benign but does not change this runtime credential transfer.
Evidence
worker.js
Network endpoints1
api.diggylab.com
Decision evidence
public snapshotAI called this Malicious at 96.0% confidence as Malware with low false-positive risk.
Evidence for block
- The worker defaults its API recipient to api.diggylab.com; an operator who leaves the default in place gets that package-selected destination.
- The login command accepts Facebook cookies or completes a browser login, then reports that the Facebook session was sent to the server.
- The browser-login path passes the captured Facebook session to the shared upload function.
- The cookie-login path validates supplied Facebook cookies and uses the same upload function.
- The shared function sends the session state to the API, and the HTTP client posts it to the worker session endpoint using its configured origin.
- Production API origins are accepted when they use HTTPS, without a recipient allowlist binding them to a user-selected host.
Evidence against
- The transfer requires the user to invoke login; the postinstall hook is limited to installing Playwright’s Chromium browser.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
5 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node worker.js install-browser
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node worker.js install-browser
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgworker.jsView file
3// src/worker/cli.ts
L4: import { spawn } from "node:child_process";
L5: import { randomUUID } from "node:crypto";
High
Findings
4 High4 Medium5 Low
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processworker.js
HighSandbox Evasion Gated Capabilityworker.js
HighRuntime Package Installworker.js
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to diggylab-worker@0.1.35.
See all versions of diggylab-worker for other recorded verdicts.
- Avoid installing diggylab-worker@0.1.35. 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.