moideva
High-performance DOM utility and diagnostic bridge for modern web applications.
This report shows the evidence for moideva@1.0.0, the only known version.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiSource establishes concrete stealth, persistence, proctoring-evasion, screen/UI capture, and automated AI-assisted cheating behavior. The benign postinstall hook does not mitigate the malicious runtime chain.
Decision evidence
public snapshot- The command-line launcher copies Electron to a Windows-like name, detaches it, and respawns it after termination.
- The Electron window is hidden from capture and actively evades Testpad and core.exe checks.
- User triggers capture screenshots or foreground-window text; the package queues that data for automated AI submission.
- The package injects captured questions and prompts into ChatGPT, then reads answers back into its hidden overlay.
- It ships a PowerShell script that decrypts Chrome-family cookies for OpenAI and ChatGPT domains.
- The package metadata and README use inconsistent names, while source explicitly targets exam/proctor evasion.
- The postinstall hook only attempts to require Electron and does not run the launcher.
- No source evidence shows captured data being sent to an attacker-controlled host.
- The cookie-extraction script is not referenced by the inspected JavaScript entrypoints.
Source & flagged code
11 flagged · loading sourceInstall-time lifecycle script matches a deterministic static-gate block pattern.
package.jsonView on unpkgPackage defines install-time lifecycle scripts.
package.jsonView on unpkgPackage source references child process execution.
bin/kalamasha-tool.jsView on unpkg · L2Findings
Affected versions and remediation
This report applies to moideva@1.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing moideva@1.0.0. 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.