Lunar Eclipse
Based on the RiskyPlugins AI security review of the observed evidence.
Analysis record
- Analysed
- 10 months ago
- Version
- v0.1.4
- Artifact
- SHA256 051…CE4
- Source
- Findings (non-IoC)
No Findings
All security checks passed
Publisher Evidence
Limited evidenceEd Heltzel
Publisher identity, store signals, distribution reach, and warning signals used for context. Treat this as supporting evidence, not a clean bill of health.
13 evidence rows available.
No Threats Detected
This extension passed all security checks
AI Security Report
AI Security Review
Evidence context: threat category none; evidence quality moderate.
The extension’s purpose is to provide a visual theme with light and dark variants. The only notable findings are YARA rules titled postinstall_system_command, postinstall_network_communication, postinstall_file_download, postinstall_file_manipulation, postinstall_obfuscation, and postinstall_persistence_mechanism reported from an "unknown_file" path. These YARA signatures belong to the documented postinstall_ code‑smell* family, which deliberately matches routine Node.js patterns such as child_process.exec, fetch, or file I/O that are common in packaging scripts. Because the rule set is designed to flag any post‑install script regardless of intent, and the extension is a theme that normally runs no build steps, these matches are interpreted as noise rather than evidence of malicious behavior. There are no findings that read credential files like .env, .ssh, or cloud configuration files, and no secret‑type detections at all. Consequently, there is no indication that the extension attempts to steal credentials or exfiltrate source code. The strongest counter‑argument would be that the repeated high‑severity YARA matches imply an active payload hidden in the post‑install script. However, all matches lack concrete file paths, reference generic rule titles, and fall under a known false‑positive category; without a verifiable executable script or network call, the suspicion cannot outweigh the established noise pattern. Therefore the extension is treated as benign, with its filesystem access limited to read‑only theme assets, which aligns with its stated functionality.
Key Reasons
- All high‑severity findings are generic postinstall YARA signatures
- No credential‑related detections were identified
- Findings reference "unknown_file", providing no actionable malicious code
- Theme extensions normally require only read‑only asset access
False Positive Considerations
- YARA postinstall code‑smell rules
- Absence of concrete file paths
- Bundled/minified theme assets
Reviewed 2026-05-23; recommended action: no action; model confidence 92%.
Source Code Not Available
Source code is not available for this version of the extension.
About This Extension
Frequently Asked Questions
Similar Extensions
Related extensions from the same publisher or marketplace