VoisaScript
The AI review rates the findings as likely false positive. The risk score (88/100) comes from stored counts that the review could not adjust. A new analysis will update it.
Analysis record
- Analysed
- 11 months ago 1 December 2025
- Version
- v1.3.1.0
- Artifact
- SHA256 26fac375…15ae49
- Detail
- Counts only, rows expired
Detail for this analysis has expired
This analysis ran on 1 December 2025. 1,050 findings counted, and the counts are kept. The individual rows have aged out of storage. A new analysis restores them.
Detail for this analysis has expired
This analysis ran on 1 December 2025. 1,420 network indicators counted, and the counts are kept. The individual rows have aged out of storage. A new analysis restores them.
Publisher Evidence
Limited evidencedev--7b29026e-f896-6628-ca93-c918f5d71e71
Publisher identity, store signals, distribution reach, and warning signals used for context. Treat this as supporting evidence, not a clean bill of health.
Chrome does not expose the same publisher verification data as IDE stores, so this score is deliberately conservative.
13 evidence rows available.
Detail for this analysis has expired
This analysis ran on 1 December 2025. 2,470 findings counted, and the counts are kept. The individual rows have aged out of storage. A new analysis restores them.
Stored counts by category
- 1,420
- Network indicators
- 998
- Malware signatures
- 994
- Code patterns
- 48
- Network calls
- 3
- Obfuscation
- 1
- Manifest
AI Security Report
AI Security Review
Evidence context: threat category none; evidence quality moderate.
VoisaScript is a Chrome extension described as "Record and Play audio comments." The extension requests the tabs permission (MANIFEST-SENSITIVE-PERM-TABS in manifest.json), which is appropriate for an audio recording tool that needs to access page content.
The evidence bundle shows 2,470 total findings, but the vast majority are documented false positive patterns. Of these, 994 are code-smell findings, which the CVEQ documentation explicitly classifies as noise—rules like postinstall_*, credential_*, and code-quality checks that fire on almost any non-trivial JavaScript. These should NEVER drive a verdict. Additionally, 1,420 IoC findings are present, but the XIOC extractor is known to produce massive false-positive volumes including IPv6 fragments, loopback addresses, and property access chains misread as domains. The network findings (48 total) show generic fetch calls in background.8bb6d83c.js, popup.5b6cf244.js, and browser-polyfill.min.4030e651.js, plus websocket connections in popup.90214440.js and VoisaScript.3156a035.js—none of which reference specific suspicious domains.
The extension's functionality aligns with its permissions: audio recording requires access to page content via the tabs permission. The network calls (fetch, websocket) are standard for extensions that need to communicate with backend services for audio processing or storage. No browser hijacking indicators (custom search engines, history API manipulation), credential theft patterns (login domain targeting), or malware delivery disguises (Flash Player, VPN lures) are present.
The strongest counterargument is the anonymous developer attribution ([email removed]) combined with only 5 users and 4 malware signature findings. A skeptic could argue this represents a low-profile malicious extension. However, the malware signatures lack specific details in the evidence, and the guidelines note that reclassified malware family rules (like Bolonyokte matching "Online Banking") are too broad and fire on legitimate code. The 3 obfuscation findings are likely false positives in locale files (zero-width Unicode characters are legitimate for South Asian scripts). The low user count could simply indicate a new or niche extension rather than malicious activity.
The evidence pattern—legitimate functionality, appropriate permissions, and findings dominated by documented false positive patterns—supports a likely_false_positive verdict. The 4 malware signatures warrant monitoring but lack the specificity needed for a confirmed_malicious determination.
Key Reasons
- 1420 IoCs are documented false positive patterns from XIOC extractor
- 994 code-smell findings are explicitly classified as noise per CVEQ guidelines
- Network findings show generic fetch/websocket without suspicious domains
- Tabs permission is appropriate for stated audio recording functionality
False Positive Considerations
- IoC extractor false positives
- Code-smell YARA rules
- Bundled dependencies
- Generic network findings
Reviewed 2026-04-30 · version 1.3.1.0; recommended action: suppress false positive; model confidence 65%.
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