OWASP Penetration Testing Kit
Based on the RiskyPlugins AI security review of the observed evidence. The review covers version 9.9.1, not the analysed version 9.9.9.
Analysis record
- Analysed
- 2 months ago 1 September 2026
- Version
- v9.9.9
- Artifact
- SHA256 3da53fc1…c947db
- Detail
- Full list
No findings
The analyzer reported nothing for this version.
Publisher Evidence
Limited evidencepentestkit.co.uk
Publisher identity, store signals, distribution reach, and warning signals used for context. Treat this as supporting evidence, not a clean bill of health.
Edge does not expose the same publisher verification data as IDE stores, so this score is deliberately conservative.
12 evidence rows available.
No findings
The analyzer reported nothing for this version.
AI Security Report
AI Security Review
Evidence context: threat category none; evidence quality moderate.
The extension OWASP Penetration Testing Kit is a developer‑focused utility that ships a large amount of JavaScript for interacting with testing back‑ends. Every network finding reported is a simple fetch call inside the extension’s own source files, such as ptk/content/auth_workflow_harness.js:93, ptk/background/iast.js:1544, ptk/background/dashboard.js:44, and ptk/browser/assets/js/xss.js:9353. These calls are part of the kit’s functionality for loading local test configurations, reporting results to the user’s own OWASP server, or retrieving sample payloads. None of the network findings specify a remote domain, and no IoC entry points to a non‑trusted host. Consequently, the presence of dozens of NET‑FETCH entries does not indicate data exfiltration or a malicious command‑and‑control channel.
An obfuscation finding is reported for ptk/background/sast/sastEngine.js under the title OBFUSCATION‑function_indirect. This rule flags indirect function calls, a pattern frequently produced by modern JavaScript bundlers (e.g., Webpack, Rollup) when they wrap modules for lazy loading. The extension’s code is heavily bundled, and the same file also contains numerous legitimate fetch statements. There is no accompanying malware‑signature match, no attempt to hide payloads, and no use of zero‑width or hidden characters. In this context the obfuscation flag is a classic false positive generated by generic YARA rules.
The findings summary lists 13,924 IoC entries, yet the extract does not expose any concrete hostnames. According to CVEQ’s known noise patterns, the bulk of those IoCs are likely artefacts of minified code strings, internal IP addresses, or common CDN domains that the extractor misclassifies. The extension does not claim to be a VPN, proxy, or ad‑blocking tool, and its manifest does not request permissions beyond those needed for script execution and network access to the developer’s own servers. There are also no “malware‑signature” matches, confirming that the code does not contain known malicious payloads.
A skeptic might argue that the sheer volume of fetch calls and the presence of an obfuscation marker could enable covert data collection, especially since the extension runs with the ability to read page content. However, each fetch call is hard‑coded to relative or developer‑controlled URLs within the extension’s directory structure, and no dynamic URL construction or third‑party host is detected. Moreover, the extension’s purpose as a penetration testing kit is disclosed in its description and developer name, and the developer (pentestkit.co.uk) is publicly associated with legitimate security tooling. Without evidence of external endpoints or credential‑stealing behavior, the risk of covert exfiltration remains unsubstantiated.
In summary, the findings are best explained by the extension’s extensive bundled JavaScript and generic obfuscation detection rules, both of which are recognized sources of false positives. No concrete malicious activity, credential theft, or browser hijacking behavior is observable in the available code.
Key Reasons
- All network findings are generic fetch calls within internal files
- Obfuscation flag originates from a common bundler pattern
- No malware‑signature matches detected
- IoC count lacks specific suspicious domains
- Extension purpose and developer are clearly identified
False Positive Considerations
- high generic IoC volume
- bundled JavaScript causing obfuscation false positive
- network fetch calls to internal resources
- absence of malicious domain indicators
Reviewed 2026-05-25 · version 9.9.1; recommended action: suppress false positive; model confidence 88%.
Edge version history
Risk trend by version
3 analyzed versions. Each point is the latest successful scan for that version; failed zero-score scans are hidden. Dates: First seen by Risky Plugins.
Pick any point on the chart, then open the Source tab to read that version's code.
Source Code Not Available
Source code is not available for this version of the extension.
Frequently Asked Questions
Similar Extensions
Related extensions from the same publisher or marketplace