moidev
High-performance DOM utility and diagnostic bridge for modern web applications.
This report shows the evidence for moidev@1.0.0, the only known version.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThis is a concrete stealth, persistence, capture, and external-submission chain, not a diagnostic utility. The benign postinstall hook does not mitigate the malicious user-executed behavior.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
User runs the moidev CLI; capture and upload are activated by global hotkey combinations.
Impact
Concealed collection and external transfer of foreground content, plus a bundled browser-session credential extractor.
Mechanism
stealth persistence, screen/UI capture, and automated AI submission
Attack narrative
After a user runs the CLI, it detaches and respawns an Electron process under the deceptive SearchApp.exe name. The app creates an overlay designed to avoid capture and specifically changes its capture-protection behavior when a proctor scanner is detected. Global hotkeys capture foreground screenshots or UI text, then inject the collected content into a hidden ChatGPT session. Separately, the package includes a PowerShell component that decrypts browser cookies for OpenAI domains.
AI rationale
This is a concrete stealth, persistence, capture, and external-submission chain, not a diagnostic utility. The benign postinstall hook does not mitigate the malicious user-executed behavior.
Evidence
package.jsonbin/kalamasha-tool.jsmain.jsbin/stealth_capture.ps1bin/uia_extract.pybin/chrome_cookies.ps1bin/uia_extract.execonfig.json%LOCALAPPDATA%\Microsoft\Windows\Diagnostics\boot.log%LOCALAPPDATA%\Microsoft\Windows\Diagnostics\.kill_watchdog
Network endpoints3
chatgpt.com/?model=autochat.openai.comipc.shadxino.internal/login_post
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- Detached launcher disguises Electron as SearchApp.exe and continuously respawns it.
- Runtime hides its window from capture and evades a detected core.exe scanner.
- Captures foreground-window images/text and injects them into ChatGPT.
- Bundled PowerShell decrypts Chrome/OpenAI session cookies using DPAPI.
Evidence against
- postinstall only attempts to require Electron; it does not run the launcher.
- Capture/strike actions are hotkey-triggered rather than install-time.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNativeBindingsShell
HighEntropyStringsUrlStrings
Source & flagged code
9 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node -e "try{require('electron')}catch(e){console.log('Electron will download on first run.')}"
Critical
Red Install Lifecycle Script
Install-time lifecycle script matches a deterministic static-gate block pattern.
package.jsonView on unpkg•scripts.postinstall = node -e "try{require('electron')}catch(e){console.log('Electron will download on first run.')}"
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkgbin/kalamasha-tool.jsView file
2L3: const { spawn, execSync } = require('child_process');
L4: const path = require('path');
High
Child Process
Package source references child process execution.
bin/kalamasha-tool.jsView on unpkg · L2Findings
1 Critical6 High4 Medium4 Low
CriticalRed Install Lifecycle Scriptpackage.json
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processbin/kalamasha-tool.js
HighShellmain.js
HighCross File Remote Execution Contextbin/kalamasha-tool.js
HighRuntime Package Installbin/kalamasha-tool.js
HighKnown Malware Source Similaritybin/kalamasha-tool.js
MediumEnvironment Vars
MediumShips Native Binarybin/uia_extract.exe
MediumShips Build Helperbin/chrome_cookies.ps1
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
Affected versions and remediation
This report applies to moidev@1.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing moidev@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.