dilema
System-wide AI overlay. Hidden from screen sharing.
This report shows the evidence for dilema@1.0.4. 3 of 5 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiSource inspection confirms deliberate third-party protected-process targeting, DLL injection, masquerading, and persistence. The lack of install-time execution does not negate the concrete malicious runtime behavior.
Decision evidence
public snapshot- `desktop/dist/daemon.cjs` finds TestPad/exam windows and injects `unprotect.dll` every 5 seconds.
- `desktop/resources/inject_dll.ps1` uses remote-thread DLL injection into another process.
- `dist/cli/index.js` disguises Electron as Microsoft Edge WebView2 and changes its version metadata.
- `dist/cli/index.js` creates a minute-by-minute `MicrosoftEdgeWebView2Update` scheduled task to resurrect the daemon.
- `cli/guard.cjs` restarts the daemon and masquerades its process title as Windows Audio Device Graph Isolation.
- `desktop/dist/daemon.cjs` captures screen content and sends it to Groq for OCR/exam answers.
- `package.json` has no preinstall, install, postinstall, or prepare lifecycle hook.
- The observed network destination is the package-aligned Groq API rather than an unknown collector.
- Persistence is activated by the explicit `dilema start` command, not on npm installation.
Source & flagged code
12 flagged · loading sourceSource spawns a local helper that also contains network and dynamic execution context; review data flow before blocking.
dist/cli/index.jsView on unpkg · L13Findings
Affected versions and remediation
This report applies to dilema@1.0.4.
The versions list below shows the verdict for each recorded version.
- Avoid installing dilema@1.0.4. 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.