registry / Credential exfiltration / diggylab-worker
diggylab-worker
DiggyLab Desktop Agent collects posts and information from Facebook Groups on a paired computer. (self-hosted scan worker)
This report shows the evidence for diggylab-worker@0.1.38. 4 of 4 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe ordinary login path sends Facebook session credentials to the package-selected default API host without recipient-specific consent. This verified credential transfer supports blocking publication.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review; source fingerprint signature matched known malicious package; routed for review
Trigger
A registered worker user runs the login command and completes browser login or supplies Facebook cookies.
Impact
The API recipient receives reusable Facebook session credentials, creating conditional exposure of the user's Facebook account.
Mechanism
The login flow posts the captured browser storage state to the API session endpoint, then stores a local copy.
Attack narrative
When a registered user logs in, the package captures Facebook cookies from browser login or pasted cookie input and sends the resulting storage state to the worker API. The default API host is selected by the package. The source does not show a recipient-specific consent step before that transfer, so the upload exposes Facebook session credentials to the package-selected recipient.
AI rationale
The ordinary login path sends Facebook session credentials to the package-selected default API host without recipient-specific consent. This verified credential transfer supports blocking publication.
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 normal login flow sends the captured Facebook session to the worker API before saving it locally.
- The API defaults to the package-selected host api.diggylab.com; the source shows no recipient-specific confirmation before the session upload.
- The login command sends sessions from both browser login and pasted-cookie login paths.
Evidence against
- The API accepts a caller-configured origin, and login prints that the Facebook session was sent to the server; these facts disclose the transfer but do not establish consent to send Facebook credentials to the default recipient.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
4 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
•matchType = normalized_sha256
matchedPackage = diggylab-worker@0.1.37
matchedPath = worker.js
matchedIdentity = npm:ZGlnZ3lsYWItd29ya2Vy:0.1.37
similarity = 1.000
summary = normalized source hash matched finalized malicious source
High
Known Malware Source Similarity
Source file is highly similar to a previously finalized malicious package; route for source-aware review.
worker.jsView on unpkgFindings
3 High4 Medium5 Low
HighInstall Time Lifecycle Scriptspackage.json
HighKnown Malware Source Similarityworker.js
HighKnown Malware Source Fingerprint Signatureworker.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.38.
The versions list below shows the verdict for each recorded version.
- Avoid installing diggylab-worker@0.1.38. 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.
Versions
4 known versions0.1.38latestshownMaliciousCredential ExfiltrationBlockPublishedOct 18, 2026, 8:37 AM0.1.37MaliciousCredential ExfiltrationBlockPublishedOct 17, 2026, 3:10 AM0.1.36MaliciousCredential ExfiltrationBlockPublishedOct 15, 2026, 12:01 PM0.1.35MaliciousCredential ExfiltrationBlockPublishedOct 15, 2026, 10:32 AM