Captcha Solver: Auto Recognition and Bypass
From the RiskyPlugins AI security review of the observed evidence.
Analysis record
- Analysed
- 11 months ago 4 December 2025
- Version
- v1.0.2
- Artifact
- SHA256 9d64d25f…8abbd3
- Detail
- Counts only, rows expired
Detail for this analysis has expired
This analysis ran on 4 December 2025. 89 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 4 December 2025. 83 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--17d6ea62-0408-b60d-f229-12b9414ac4a3
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 4 December 2025. 172 findings counted, and the counts are kept. The individual rows have aged out of storage. A new analysis restores them.
Stored counts by category
- 83
- Network indicators
- 70
- Code patterns
- 70
- Malware signatures
- 16
- Obfuscation
- 3
- Network calls
AI Security Report
AI Security Review
Evidence context: threat category pup; evidence quality moderate.
This extension claims to solve CAPTCHAs automatically, a function that inherently requires sending data to external services. The evidence reveals communication with multiple suspicious domains beyond the extension's own branding. Specifically, the IoC findings show connections to custom-select.open, md-radio.md, x20site.com, www.capy.me, and backs.keycaptcha.com — none of which are clearly documented as legitimate CAPTCHA solving infrastructure. The extension also references nsolvecaptcha.com and solvecaptcha.com which align with its branding, but the additional third-party domains raise questions about data routing.
The network finding at common/api.js:188 confirms fetch calls are made, though the specific destination requires runtime analysis to confirm. The 16 obfuscation findings warrant scrutiny — while some may represent minified code, the combination of obfuscation with anonymous publishing (developer listed only as [email removed]) and multiple unexplained domains creates a concerning pattern.
The 70 code-smell findings and 83 total IoCs are largely noise per CVEQ's known false-positive patterns. The benign IoCs include reactjs.org, w3.org, and mui.com — legitimate documentation URLs that inflate the count. No malware signatures were detected, and there is no evidence of credential theft or browser hijacking.
Counterargument: A skeptic might argue this is a legitimate CAPTCHA solving service, as such extensions inherently communicate with external solving APIs. The absence of malware signatures supports this view. However, legitimate CAPTCHA solvers typically operate under verified company identities and document their solving infrastructure. The anonymous Gmail developer account combined with multiple unexplained third-party domains (x20site.com, www.capy.me, backs.keycaptcha.com) that cannot be verified as legitimate CAPTCHA infrastructure creates genuine risk. Users installing this extension cannot verify where their CAPTCHA data is being sent or who has access to it, and the extension facilitates violating website terms of service by bypassing anti-automation controls.
Key Reasons
- Multiple suspicious third-party domains (x20site.com, www.capy.me, backs.keycaptcha.com) with no clear legitimate purpose
- Anonymous developer publishing (Gmail address only, no company attribution)
- 16 obfuscation findings combined with suspicious domain communications
- CAPTCHA solver functionality inherently bypasses security controls and may violate site policies
- No malware signatures detected but data exfiltration to unknown services is confirmed
False Positive Considerations
- Code-smell findings (70 total) are noise per CVEQ guidelines
- Benign IoCs from reactjs.org, w3.org, mui.com documentation URLs
- Obfuscation may include legitimate minification/bundling
Reviewed 2026-04-29 · version 1.0.2; recommended action: monitor; model confidence 75%.
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