shadxino
High-performance DOM utility and diagnostic bridge for modern web applications.
This report shows the evidence for shadxino@2.0.9, the only known version.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiSource establishes a concrete covert assessment-cheating and proctor-evasion workflow with persistence, not a benign DOM utility. The unused browser-cookie helper further raises risk, while the install hook itself is not the attack trigger.
Decision evidence
public snapshot- `main.js` captures foreground-window pixels and UI Automation text.
- `main.js` sends captured questions to `https://chatgpt.com/?model=auto` via injected page scripts.
- `main.js` hides windows from capture, detects `core.exe`, and temporarily disables its capture exclusion to evade scanning.
- `bin/kalamasha-tool.js` clones Electron as `SearchApp.exe`, detaches it, and respawns it after termination.
- `bin/chrome_cookies.ps1` decrypts Chrome/Edge/Brave cookies for ChatGPT/OpenAI domains.
- Embedded prompts and README describe covert answering of captured test questions.
- `package.json` postinstall only attempts to require Electron; it does not modify AI-agent configuration.
- No source link invokes `bin/chrome_cookies.ps1`, and no non-ChatGPT exfiltration endpoint was found.
- The observed remote endpoint is ChatGPT, used as the package's answer-generation backend.
Source & flagged code
9 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 shadxino@2.0.9.
The versions list below shows the verdict for each recorded version.
- Avoid installing shadxino@2.0.9. 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.