APIVoid Full Page Capture
The AI review rates the findings as likely false positive, but the risk score (51/100) still counts them.
Analysis record
- Analysed
- 3 months ago
- Version
- v1.1
- Artifact
- SHA256 07B…B7F
- Source
- Findings (non-IoC)
Evidence ledger
Ranked by severity · findings with a source location link to the code viewer
Network Indicators
Concrete URLs, domains, IPs, emails, and hashes extracted from the analyzed artifact.
Network indicators are queued for lazy loading
Scroll this section into view to load the detailed rows.
Publisher Evidence
Limited evidenceAPIVoid
Publisher identity, store signals, distribution reach, and warning signals used for context. Treat this as supporting evidence, not a clean bill of health.
Firefox does not expose the same publisher verification data as IDE stores, so this score is deliberately conservative.
12 evidence rows available.
Finding Categories
Requested Permissions
6 permissionsAccess and modify data on every website you visit
Manage, modify, and monitor downloads
AI Security Report
AI Security Review
Risky Plugins reviewed this extension with an AI-assisted security workflow on 2026-05-31. The review verdict is likely false positive with 80% confidence.
Recommended action: no action. Evidence context: threat category none; evidence quality moderate.
The APIVoid Full Page Capture extension has a high number of IoC findings, primarily due to XIOC detections of various domains such as apivoid.com, a.download, and chromewebstore.google.com. However, these findings are likely driven by the extension's functionality to capture and save screenshots, which may involve communicating with external services. Notably, there are no malware signatures or obfuscation findings, which reduces the likelihood of malicious intent. The network finding in background.js:24 is a fetch call, which is a common and legitimate operation for extensions. A potential counterargument could be that the extension's lack of developer information and low user count raises suspicions. However, given the absence of concrete evidence of malicious behavior and the plausible explanation for the IoC findings, this concern is mitigated. The strongest counterargument to the verdict would be the presence of suspicious domains like a.click and delta.id, but without additional context or evidence of malicious use, these alone do not conclusively indicate harmful activity.
Key Reasons
- No malware signatures detected
- IoC findings explainable by extension functionality
- Network finding is a common and legitimate operation
False Positive Considerations
- IoC extractor garbage
- XIOC false positives
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