diggylab-worker@0.1.36
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 explicit login path transfers Facebook session cookies to the package's default API, a recipient separate from Facebook, without recipient-specific consent. Because the cookies can authenticate the Facebook account, this is concrete credential disclosure.
Decision evidence
public snapshot- The login flow obtains a Facebook session through browser login or supplied cookies, then passes it to the session upload helper.
- The helper sends the session data in a POST to the worker session endpoint; requests use the configured API origin.
- The default recipient is api.diggylab.com. The API origin can be set by the caller, and packaged destinations are accepted over HTTPS without a host allowlist.
- The code saves a local session copy after the upload; the login flow has no recipient-specific consent check.
- The transfer happens when the operator invokes login, and the worker validates the Facebook session before uploading it.
Source & flagged code
5 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to diggylab-worker@0.1.36.
See all versions of diggylab-worker for other recorded verdicts.
- Avoid installing diggylab-worker@0.1.36. 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.