Extension
The AI review rates the findings as likely false positive, but the risk score (86/100) still counts them. The review covers version 9.9.1, not the analysed version 9.9.10.
Analysis record
- Analysed
- 6 days ago 16 November 2026
- Version
- v9.9.10
- Artifact
- SHA256 d41686e9…42d988
- Detail
- Partial list
Evidence ledger
Ranked by severity · findings with a source location link to the code viewer
YARA Rule Matches
9 rules| Severity | Rule | Hits | Files | Metadata |
|---|---|---|---|---|
| HIGH | IronTiger ASPXSpy ASPXSpy detection. It might be used by other fraudsters | 1 | ptk/background/paths.txt | Cyber Safety Solutions, Trend Micro FP 5% |
| HIGH | ccrewQAZ | 1 | ptk/background/jwt.secrets.list.txt | AlienVault Labs FP 70% |
| LOW | postinstall crypto operations | 327 | ptk/packages/crypto-es/mode-ecb.cjsptk/packages/crypto-es/sha256.mjsptk/common/zapLifecycle.js +324 more | - |
| LOW | postinstall file manipulation | 229 | ptk/packages/lodash-es/array.jsptk/background/session.jsptk/packages/crypto-es/core.d.cts +226 more | - |
| LOW | postinstall environment access | 84 | ptk/packages/lodash-es/util.jsptk/packages/lodash-es/_parent.jsptk/background/analysis/attackSurfaceRecommendations.js +81 more | - |
| LOW | postinstall obfuscation | 2 | ptk/browser/assets/js/findingNormalizer.jsptk/background/sast/sastEngine.js | - |
| LOW | postinstall system command | 162 | ptk/packages/wappalyzer/htmlRules.jsptk/browser/sql.htmlptk/background/dast/modules/module.js +159 more | - |
| LOW | credential gcp config | 1 | ptk/background/paths.txt | - |
| LOW | postinstall network communication | 127 | ptk/controller/rbuilder.jsptk/packages/semantic-ui/semantic.min.cssptk/background/sast/modules/modules.json +124 more | - |
Network Indicators
Concrete URLs, domains, IPs, emails, and hashes extracted from the analyzed artifact.
Loading network indicators
Long lists can take a few seconds.
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.
Firefox does not expose the same publisher verification data as IDE stores, so this score is deliberately conservative.
13 evidence rows available.
Finding Categories
YARA Rules Matched
9 rules(934 hits)Requested Permissions
12 permissionsAccess and modify data on every website you visit
Read and modify cookies on all sites
Intercept, modify, and block all network requests
Block network requests before they complete
AI Security Report
AI Security Review
Evidence context: threat category none; evidence quality moderate.
This extension, described as a 'Penetration Testing Kit' for security practitioners, generates 13,991 total findings but contains zero malware signatures and zero malware detections. The finding distribution reveals 13,932 IoC findings, 54 network findings, 3 obfuscation findings, and 2 manifest analysis findings. The IoC count is characteristic of known false-positive patterns from the CVEQ XIOC extractor, which produces garbage matches on IPv6 fragments (e.g., ::, ::b), hex substrings from minified JavaScript, and property access chains misread as domains.
The 54 network findings are all fetch calls in files with legitimate security testing module names: ptk/background/iast.js (Interactive Application Security Testing), ptk/background/dast/dastEngine.js (Dynamic Application Security Testing), ptk/background/sast/sast_portal_client.js (Static Application Security Testing), ptk/background/sca.js (Software Composition Analysis), and ptk/background/rattacker.js. These file paths and functionality align with expected behavior for a penetration testing tool that needs to communicate with security analysis services and dashboards.
Crucially, there are zero code-smell findings, zero malware-family signatures, and zero credential theft patterns. The two high-severity findings are unspecified but without malware signatures they lack malicious context. The three obfuscation findings are minimal and do not co-locate with malware signatures in the same files.
The strongest counterargument is the empty developer name field, which violates best practices for extension publishing. A skeptic could argue this anonymity combined with high finding counts warrants a confirmed_risk verdict. However, the empty developer name alone does not constitute malicious evidence. The actual code behavior—fetch calls in security testing modules with zero malware signatures—is consistent with legitimate penetration testing functionality. The finding volume is explained by known IoC extractor false-positive patterns, not malicious domain communication. Without malware signatures, credential theft patterns, or browser hijacking behavior, the empty developer name is a metadata concern rather than a security threat.
Key Reasons
- Zero malware signatures and zero malware detections in 13,991 findings
- 13,932 IoC findings match known false-positive patterns (IoC extractor garbage)
- Network findings are fetch calls in legitimate security testing modules (IaST, DAST, SAST, SCA)
- Zero code-smell findings indicates no suspicious code patterns
- File paths and functionality consistent with legitimate penetration testing tool
False Positive Considerations
- IoC extractor garbage (IPv6 fragments, hex substrings, property chains)
- High finding count in bundled/complex extension code
- Network findings from legitimate fetch calls in security testing modules
Reviewed 2026-05-08 · version 9.9.1; recommended action: suppress false positive; model confidence 75%.
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
OWASP Penetration Testing Kit
Unknown Developer
OWASP PenTestKit Automation
pentestkit.co.uk
Falcon Secure Access Extension - Connect
Seraphic Algorithms
VaultysHub extension
Vaultys
Kindredly - A better web
Kindredly.ai
VHS - Dev Tools
Vihat Software