[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6HNB2WDZ3YYYNAVSWPHXQG3":3,"skill-same:01M6HNB2WDZ3YYYNAVSWPHXQG3":119},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":62,"commitSha":63,"skillDirectory":64,"forksCount":65,"repositoryHtmlUrl":66,"repositoryHomepageUrl":6,"ownerHtmlUrl":67,"ownerBlogUrl":6,"ownerDescription":68,"updatedAt":69,"install":70,"resources":83},"01M6HNB2WDZ3YYYNAVSWPHXQG3","performing-mobile-app-certificate-pinning-bypass",null,"Bypasses SSL\u002FTLS certificate pinning implementations in Android and iOS applications to enable traffic interception during authorized security assessments. Covers OkHttp, TrustManager, NSURLSession, and third-party pinning library bypass...","HenriqueMC17\u002Fagente-core","HenriqueMC17","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F206460478?v=4","01M6HB63HBBF18AC4H09XTB549","Henrique Monteiro Cardoso","01M6HB63NGSQXWKWCFWW2B20W0",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fperforming-mobile-app-certificate-pinning-bypass\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"certificate","performing","app","mobile","mobile app","performing mobile app certificate pinning bypass","t1059","applications","certificate-pinning","tls","testing","PS","ssl","cm","pr","cybersecurity","id","penetration","traffic","android","2026-11-10 10:12:30",false,"---\nname: performing-mobile-app-certificate-pinning-bypass\ndescription: Bypasses SSL\u002FTLS certificate pinning implementations in Android and iOS applications to enable traffic interception during authorized security assessments. Covers OkHttp, TrustManager, NSURLSession, and third-party pinning library bypass...\ndomain: cybersecurity\nsubdomain: mobile-security\nauthor: mahipal\ntags:\n- mobile-security\n- android\n- ios\n- certificate-pinning\n- frida\n- penetration-testing\nversion: 1.0.0\nlicense: Apache-2.0\nnist_csf:\n- PR.PS-01\n- PR.AA-05\n- ID.RA-01\n- DE.CM-09\nmitre_attack:\n- T1059\n- T1056\n- T1036\n- T1078\n- T1027\ncategory: performing-mobile-app-certificate-pinning-bypass\n---\n# Performing-Mobile-App-Certificate-Pinning-Bypass\n\n## Overview\nBypasses SSL\u002FTLS certificate pinning implementations in Android and iOS applications to enable traffic interception during authorized security assessments. Covers OkHttp, TrustManager, NSURLSession, and third-party pinning library bypass techniques using Frida, Objection, and custom scripts. Activates for requests involving certificate pinning bypass, SSL pinning defeat, mobile TLS interception, or proxy-resistant app testing.\n\n\n# Performing Mobile App Certificate Pinning Bypass\n\n## When to Use\n\nUse this skill when:\n- Mobile app refuses connections through a proxy due to certificate pinning\n- Performing authorized security testing requiring HTTPS traffic interception\n- Assessing the strength and bypass difficulty of pinning implementations\n- Evaluating defense-in-depth of mobile app network security\n\n**Do not use** to bypass pinning on apps without explicit testing authorization.\n\n## Prerequisites\n\n- Burp Suite configured as proxy with listener on all interfaces\n- Rooted Android device or jailbroken iOS device\n- Frida server running on target device\n- Objection installed (`pip install objection`)\n- Target app installed and reproducing the pinning behavior\n\n## Workflow\n\n### Step 1: Identify Pinning Implementation\n\n**Android pinning methods to identify:**\n```\n1. Network Security Config (res\u002Fxml\u002Fnetwork_security_config.xml)\n   \u003Cpin-set> with certificate hash pins\n\n2. OkHttp CertificatePinner\n   CertificatePinner.Builder().add(\"api.target.com\", \"sha256\u002F...\")\n\n3. Custom TrustManager\n   X509TrustManager overrides in code\n\n4. Third-party libraries\n   - TrustKit\n   - Certificate Transparency checks\n```\n\n**iOS pinning methods:**\n```\n1. NSURLSession delegate (URLSession:didReceiveChallenge:)\n2. ATS (App Transport Security) with custom trust evaluation\n3. TrustKit framework\n4. Alamofire ServerTrustPolicy\n5. Custom SecTrust evaluation\n```\n\n### Step 2: Bypass with Objection (Quickest Approach)\n\n```bash\n# Android\nobjection --gadget com.target.app explore\nandroid sslpinning disable\n\n# iOS\nobjection --gadget com.target.app explore\nios sslpinning disable\n```\n\nObjection hooks common pinning implementations including OkHttp CertificatePinner, TrustManagerImpl, NSURLSession delegate methods, and SecTrust evaluation.\n\n### Step 3: Bypass with Custom Frida Scripts\n\n**Android - Universal SSL Pinning Bypass:**\n```javascript\n\u002F\u002F android_ssl_bypass.js\nJava.perform(function() {\n    \u002F\u002F Bypass TrustManagerImpl\n    var TrustManagerImpl = Java.use(\"com.android.org.conscrypt.TrustManagerImpl\");\n    TrustManagerImpl.verifyChain.implementation = function(untrustedChain, trustAnchorChain,\n        host, clientAuth, ocspData, tlsSctData) {\n        console.log(\"[+] Bypassing TrustManagerImpl for: \" + host);\n        return untrustedChain;\n    };\n\n    \u002F\u002F Bypass OkHttp3 CertificatePinner\n    try {\n        var CertificatePinner = Java.use(\"okhttp3.CertificatePinner\");\n        CertificatePinner.check.overload(\"java.lang.String\", \"java.util.List\").implementation =\n            function(hostname, peerCertificates) {\n                console.log(\"[+] Bypassing OkHttp3 pinning for: \" + hostname);\n                return;\n            };\n    } catch(e) {}\n\n    \u002F\u002F Bypass custom X509TrustManager\n    var X509TrustManager = Java.use(\"javax.net.ssl.X509TrustManager\");\n    var TrustManager = Java.registerClass({\n        name: \"com.bypass.TrustManager\",\n        implements: [X509TrustManager],\n        methods: {\n            checkClientTrusted: function(chain, authType) {},\n            checkServerTrusted: function(chain, authType) {},\n            getAcceptedIssuers: function() { return []; }\n        }\n    });\n\n    \u002F\u002F Bypass SSLContext\n    var SSLContext = Java.use(\"javax.net.ssl.SSLContext\");\n    SSLContext.init.overload(\"[Ljavax.net.ssl.KeyManager;\",\n        \"[Ljavax.net.ssl.TrustManager;\", \"java.security.SecureRandom\").implementation =\n        function(km, tm, sr) {\n            console.log(\"[+] Replacing TrustManagers in SSLContext.init\");\n            this.init(km, [TrustManager.$new()], sr);\n        };\n\n    \u002F\u002F Bypass NetworkSecurityConfig (Android 7+)\n    try {\n        var NetworkSecurityConfig = Java.use(\n            \"android.security.net.config.NetworkSecurityConfig\");\n        NetworkSecurityConfig.isCleartextTrafficPermitted.implementation = function() {\n            return true;\n        };\n    } catch(e) {}\n\n    console.log(\"[*] SSL pinning bypass loaded\");\n});\n```\n\n```bash\nfrida -U -f com.target.app -l android_ssl_bypass.js --no-pause\n```\n\n**iOS - Universal SSL Pinning Bypass:**\n```javascript\n\u002F\u002F ios_ssl_bypass.js\nif (ObjC.available) {\n    \u002F\u002F Bypass NSURLSession delegate\n    var resolver = new ApiResolver(\"objc\");\n    resolver.enumerateMatches(\n        \"-[* URLSession:didReceiveChallenge:completionHandler:]\", {\n        onMatch: function(match) {\n            Interceptor.attach(match.address, {\n                onEnter: function(args) {\n                    var completionHandler = new ObjC.Block(args[4]);\n                    var NSURLSessionAuthChallengeUseCredential = 0;\n                    var trust = new ObjC.Object(args[3])\n                        .protectionSpace().serverTrust();\n                    var credential = ObjC.classes.NSURLCredential\n                        .credentialForTrust_(trust);\n                    completionHandler.invoke(NSURLSessionAuthChallengeUseCredential,\n                        credential);\n                }\n            });\n        },\n        onComplete: function() {}\n    });\n\n    \u002F\u002F Bypass SecTrustEvaluate\n    var SecTrustEvaluateWithError = Module.findExportByName(\n        \"Security\", \"SecTrustEvaluateWithError\");\n    if (SecTrustEvaluateWithError) {\n        Interceptor.replace(SecTrustEvaluateWithError, new NativeCallback(\n            function(trust, error) {\n                return 1;  \u002F\u002F Always return true\n            }, \"bool\", [\"pointer\", \"pointer\"]\n        ));\n    }\n\n    console.log(\"[*] iOS SSL pinning bypass loaded\");\n}\n```\n\n### Step 4: Handle Advanced Pinning\n\nFor apps using advanced pinning (TrustKit, custom binary checks):\n\n```bash\n# Identify the specific pinning library\nfrida-trace -U -n TargetApp -m \"*[*Trust*]\" -m \"*[*Pin*]\" -m \"*[*SSL*]\" -m \"*[*Certificate*]\"\n\n# Hook the identified validation function\n# Custom Frida script targeting the specific implementation\n```\n\n### Step 5: Verify Bypass Success\n\nAfter applying the bypass:\n1. Configure device proxy to Burp Suite\n2. Open target app and navigate through authenticated flows\n3. Verify HTTPS traffic appears in Burp Suite HTTP History\n4. Check for any remaining pinned connections that are not captured\n\n## Key Concepts\n\n| Term | Definition |\n|------|-----------|\n| **Certificate Pinning** | Restricting accepted server certificates to a known set, preventing MITM via rogue CA certificates |\n| **Public Key Pinning** | Pinning the server's public key hash rather than the full certificate, surviving certificate rotation |\n| **Network Security Config** | Android XML configuration for declaring trust anchors, pins, and cleartext policy per-domain |\n| **TrustKit** | Open-source library implementing certificate pinning with reporting for both Android and iOS |\n| **HPKP Deprecation** | HTTP Public Key Pinning header was deprecated in browsers but concept persists in mobile apps |\n\n## Tools & Systems\n\n- **Objection**: Pre-built pinning bypass for common libraries (OkHttp, NSURLSession, TrustKit)\n- **Frida**: Custom JavaScript hooks targeting specific pinning implementations\n- **apktool**: APK decompilation for identifying pinning in Network Security Config\n- **SSLUnpinning (Xposed)**: Xposed framework module for system-wide pinning bypass on Android\n- **ssl-kill-switch2**: iOS tweak for disabling SSL pinning system-wide on jailbroken devices\n\n## Common Pitfalls\n\n- **Certificate transparency**: Some apps check CT logs in addition to pinning. May need to bypass CT verification separately.\n- **Multi-layer pinning**: Apps may implement pinning at multiple levels (OkHttp + custom TrustManager). Bypass all layers.\n- **Binary-level pinning**: Some apps validate certificates in native C\u002FC++ code, which requires Interceptor.attach at native function addresses rather than Java\u002FObjC hooks.\n- **Dynamic pinning updates**: Apps using TrustKit or similar may fetch updated pins from a server. Monitor for pin rotation during testing.\n","# Performing-Mobile-App-Certificate-Pinning-Bypass\n\n## Overview\nBypasses SSL\u002FTLS certificate pinning implementations in Android and iOS applications to enable traffic interception during authorized security assessments. Covers OkHttp, TrustManager, NSURLSession, and third-party pinning library bypass techniques using Frida, Objection, and custom scripts. Activates for requests involving certificate pinning bypass, SSL pinning defeat, mobile TLS interception, or proxy-resistant app testing.\n\n\n# Performing Mobile App Certificate Pinning Bypass\n\n## When to Use\n\nUse this skill when:\n- Mobile app refuses connections through a proxy due to certificate pinning\n- Performing authorized security testing requiring HTTPS traffic interception\n- Assessing the strength and bypass difficulty of pinning implementations\n- Evaluating defense-in-depth of mobile app network security\n\n**Do not use** to bypass pinning on apps without explicit testing authorization.\n\n## Prerequisites\n\n- Burp Suite configured as proxy with listener on all interfaces\n- Rooted Android device or jailbroken iOS device\n- Frida server running on target device\n- Objection installed (`pip install objection`)\n- Target app installed and reproducing the pinning behavior\n\n## Workflow\n\n### Step 1: Identify Pinning Implementation\n\n**Android pinning methods to identify:**\n```\n1. Network Security Config (res\u002Fxml\u002Fnetwork_security_config.xml)\n   \u003Cpin-set> with certificate hash pins\n\n2. OkHttp CertificatePinner\n   CertificatePinner.Builder().add(\"api.target.com\", \"sha256\u002F...\")\n\n3. Custom TrustManager\n   X509TrustManager overrides in code\n\n4. Third-party libraries\n   - TrustKit\n   - Certificate Transparency checks\n```\n\n**iOS pinning methods:**\n```\n1. NSURLSession delegate (URLSession:didReceiveChallenge:)\n2. ATS (App Transport Security) with custom trust evaluation\n3. TrustKit framework\n4. Alamofire ServerTrustPolicy\n5. Custom SecTrust evaluation\n```\n\n### Step 2: Bypass with Objection (Quickest Approach)\n\n```bash\n# Android\nobjection --gadget com.target.app explore\nandroid sslpinning disable\n\n# iOS\nobjection --gadget com.target.app explore\nios sslpinning disable\n```\n\nObjection hooks common pinning implementations including OkHttp CertificatePinner, TrustManagerImpl, NSURLSession delegate methods, and SecTrust evaluation.\n\n### Step 3: Bypass with Custom Frida Scripts\n\n**Android - Universal SSL Pinning Bypass:**\n```javascript\n\u002F\u002F android_ssl_bypass.js\nJava.perform(function() {\n    \u002F\u002F Bypass TrustManagerImpl\n    var TrustManagerImpl = Java.use(\"com.android.org.conscrypt.TrustManagerImpl\");\n    TrustManagerImpl.verifyChain.implementation = function(untrustedChain, trustAnchorChain,\n        host, clientAuth, ocspData, tlsSctData) {\n        console.log(\"[+] Bypassing TrustManagerImpl for: \" + host);\n        return untrustedChain;\n    };\n\n    \u002F\u002F Bypass OkHttp3 CertificatePinner\n    try {\n        var CertificatePinner = Java.use(\"okhttp3.CertificatePinner\");\n        CertificatePinner.check.overload(\"java.lang.String\", \"java.util.List\").implementation =\n            function(hostname, peerCertificates) {\n                console.log(\"[+] Bypassing OkHttp3 pinning for: \" + hostname);\n                return;\n            };\n    } catch(e) {}\n\n    \u002F\u002F Bypass custom X509TrustManager\n    var X509TrustManager = Java.use(\"javax.net.ssl.X509TrustManager\");\n    var TrustManager = Java.registerClass({\n        name: \"com.bypass.TrustManager\",\n        implements: [X509TrustManager],\n        methods: {\n            checkClientTrusted: function(chain, authType) {},\n            checkServerTrusted: function(chain, authType) {},\n            getAcceptedIssuers: function() { return []; }\n        }\n    });\n\n    \u002F\u002F Bypass SSLContext\n    var SSLContext = Java.use(\"javax.net.ssl.SSLContext\");\n    SSLContext.init.overload(\"[Ljavax.net.ssl.KeyManager;\",\n        \"[Ljavax.net.ssl.TrustManager;\", \"java.security.SecureRandom\").implementation =\n        function(km, tm, sr) {\n            console.log(\"[+] Replacing TrustManagers in SSLContext.init\");\n            this.init(km, [TrustManager.$new()], sr);\n        };\n\n    \u002F\u002F Bypass NetworkSecurityConfig (Android 7+)\n    try {\n        var NetworkSecurityConfig = Java.use(\n            \"android.security.net.config.NetworkSecurityConfig\");\n        NetworkSecurityConfig.isCleartextTrafficPermitted.implementation = function() {\n            return true;\n        };\n    } catch(e) {}\n\n    console.log(\"[*] SSL pinning bypass loaded\");\n});\n```\n\n```bash\nfrida -U -f com.target.app -l android_ssl_bypass.js --no-pause\n```\n\n**iOS - Universal SSL Pinning Bypass:**\n```javascript\n\u002F\u002F ios_ssl_bypass.js\nif (ObjC.available) {\n    \u002F\u002F Bypass NSURLSession delegate\n    var resolver = new ApiResolver(\"objc\");\n    resolver.enumerateMatches(\n        \"-[* URLSession:didReceiveChallenge:completionHandler:]\", {\n        onMatch: function(match) {\n            Interceptor.attach(match.address, {\n                onEnter: function(args) {\n                    var completionHandler = new ObjC.Block(args[4]);\n                    var NSURLSessionAuthChallengeUseCredential = 0;\n                    var trust = new ObjC.Object(args[3])\n                        .protectionSpace().serverTrust();\n                    var credential = ObjC.classes.NSURLCredential\n                        .credentialForTrust_(trust);\n                    completionHandler.invoke(NSURLSessionAuthChallengeUseCredential,\n                        credential);\n                }\n            });\n        },\n        onComplete: function() {}\n    });\n\n    \u002F\u002F Bypass SecTrustEvaluate\n    var SecTrustEvaluateWithError = Module.findExportByName(\n        \"Security\", \"SecTrustEvaluateWithError\");\n    if (SecTrustEvaluateWithError) {\n        Interceptor.replace(SecTrustEvaluateWithError, new NativeCallback(\n            function(trust, error) {\n                return 1;  \u002F\u002F Always return true\n            }, \"bool\", [\"pointer\", \"pointer\"]\n        ));\n    }\n\n    console.log(\"[*] iOS SSL pinning bypass loaded\");\n}\n```\n\n### Step 4: Handle Advanced Pinning\n\nFor apps using advanced pinning (TrustKit, custom binary checks):\n\n```bash\n# Identify the specific pinning library\nfrida-trace -U -n TargetApp -m \"*[*Trust*]\" -m \"*[*Pin*]\" -m \"*[*SSL*]\" -m \"*[*Certificate*]\"\n\n# Hook the identified validation function\n# Custom Frida script targeting the specific implementation\n```\n\n### Step 5: Verify Bypass Success\n\nAfter applying the bypass:\n1. Configure device proxy to Burp Suite\n2. Open target app and navigate through authenticated flows\n3. Verify HTTPS traffic appears in Burp Suite HTTP History\n4. Check for any remaining pinned connections that are not captured\n\n## Key Concepts\n\n| Term | Definition |\n|------|-----------|\n| **Certificate Pinning** | Restricting accepted server certificates to a known set, preventing MITM via rogue CA certificates |\n| **Public Key Pinning** | Pinning the server's public key hash rather than the full certificate, surviving certificate rotation |\n| **Network Security Config** | Android XML configuration for declaring trust anchors, pins, and cleartext policy per-domain |\n| **TrustKit** | Open-source library implementing certificate pinning with reporting for both Android and iOS |\n| **HPKP Deprecation** | HTTP Public Key Pinning header was deprecated in browsers but concept persists in mobile apps |\n\n## Tools & Systems\n\n- **Objection**: Pre-built pinning bypass for common libraries (OkHttp, NSURLSession, TrustKit)\n- **Frida**: Custom JavaScript hooks targeting specific pinning implementations\n- **apktool**: APK decompilation for identifying pinning in Network Security Config\n- **SSLUnpinning (Xposed)**: Xposed framework module for system-wide pinning bypass on Android\n- **ssl-kill-switch2**: iOS tweak for disabling SSL pinning system-wide on jailbroken devices\n\n## Common Pitfalls\n\n- **Certificate transparency**: Some apps check CT logs in addition to pinning. May need to bypass CT verification separately.\n- **Multi-layer pinning**: Apps may implement pinning at multiple levels (OkHttp + custom TrustManager). Bypass all layers.\n- **Binary-level pinning**: Some apps validate certificates in native C\u002FC++ code, which requires Interceptor.attach at native function addresses rather than Java\u002FObjC hooks.\n- **Dynamic pinning updates**: Apps using TrustKit or similar may fetch updated pins from a server. Monitor for pin rotation during testing.\n",{"name":5,"tags":44,"author":49,"domain":34,"license":15,"version":50,"category":5,"nist_csf":51,"subdomain":45,"description":7,"mitre_attack":56},[45,38,46,27,47,48],"mobile-security","ios","frida","penetration-testing","mahipal","1.0.0",[52,53,54,55],"PR.PS-01","PR.AA-05","ID.RA-01","DE.CM-09",[57,58,59,60,61],"T1059","T1056","T1036","T1078","T1027","main","5eea5b3296f4673b5f481e8bcc1ba76281149f16","modules\u002Fperforming-mobile-app-certificate-pinning-bypass",0,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core","https:\u002F\u002Fgithub.com\u002FHenriqueMC17","Qualquer tecnologia suficientemente avançada é indistinguível da mágica.","2026-09-28 22:40:38",{"source":8,"skillName":5,"commands":71,"prompt":81,"zipAvailable":82},[72,75,78],{"tool":73,"command":74},"npx","npx skills add HenriqueMC17\u002Fagente-core --skill performing-mobile-app-certificate-pinning-bypass",{"tool":76,"command":77},"bunx","bunx skills add HenriqueMC17\u002Fagente-core --skill performing-mobile-app-certificate-pinning-bypass",{"tool":79,"command":80},"pnpm","pnpm dlx skills add HenriqueMC17\u002Fagente-core --skill performing-mobile-app-certificate-pinning-bypass","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fperforming-mobile-app-certificate-pinning-bypass\u002FSKILL.md",true,[84,90,95,101,105,109,115],{"path":85,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":88,"sourceHtmlUrl":89},"assets\u002Ftemplate.md","ASSET","资产文件",560,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fperforming-mobile-app-certificate-pinning-bypass\u002Fassets\u002Ftemplate.md",{"path":91,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":93,"sourceHtmlUrl":94},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fperforming-mobile-app-certificate-pinning-bypass\u002FLICENSE",{"path":96,"resourceType":97,"resourceTypeDesc":98,"sizeBytes":99,"sourceHtmlUrl":100},"references\u002Fapi-reference.md","REFERENCE","参考文档",1506,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fperforming-mobile-app-certificate-pinning-bypass\u002Freferences\u002Fapi-reference.md",{"path":102,"resourceType":97,"resourceTypeDesc":98,"sizeBytes":103,"sourceHtmlUrl":104},"references\u002Fstandards.md",760,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fperforming-mobile-app-certificate-pinning-bypass\u002Freferences\u002Fstandards.md",{"path":106,"resourceType":97,"resourceTypeDesc":98,"sizeBytes":107,"sourceHtmlUrl":108},"references\u002Fworkflows.md",1554,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fperforming-mobile-app-certificate-pinning-bypass\u002Freferences\u002Fworkflows.md",{"path":110,"resourceType":111,"resourceTypeDesc":112,"sizeBytes":113,"sourceHtmlUrl":114},"scripts\u002Fagent.py","SCRIPT","脚本",6878,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fperforming-mobile-app-certificate-pinning-bypass\u002Fscripts\u002Fagent.py",{"path":116,"resourceType":111,"resourceTypeDesc":112,"sizeBytes":117,"sourceHtmlUrl":118},"scripts\u002Fprocess.py",5421,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fperforming-mobile-app-certificate-pinning-bypass\u002Fscripts\u002Fprocess.py",[120,150,176,199,215,235],{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":131,"publishedAt":39},"01M6HPFF0RCN0X6WT5EBSV71GY","validating-backup-integrity-for-recovery","Validate backup integrity through cryptographic hash verification, automated restore testing, corruption detection, and recoverability checks to ensure backups are reliable for disaster recovery and ransomware response scenarios.","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fvalidating-backup-integrity-for-recovery\u002FSKILL.md",[126],{"categoryNo":127,"categoryName":128,"taxonomyType":129,"taxonomyTypeDesc":130},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[132,133,134,135,136,29,34,137,138,139,140,141,142,143,144,145,146,147,148,149],"integrity","backup","recovery","validating backup integrity for recovery","for","validate","verification","hash-verification","incident-response","ransomware","detection","t1078","t1490","disaster-recovery","restore","incident","disaster recovery","ransomware response",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":156,"publishedAt":39},"01M6HPFAWJVFK25Q33K3T7WQ8G","triaging-vulnerabilities-with-ssvc-framework","Triage and prioritize vulnerabilities using CISA's Stakeholder-Specific Vulnerability Categorization (SSVC) decision tree framework to produce actionable remediation priorities.","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftriaging-vulnerabilities-with-ssvc-framework\u002FSKILL.md",[],[157,158,159,160,161,34,162,163,164,165,166,167,168,169,170,171,172,173,174,175],"vulnerabilities","framework","ssvc","triaging vulnerabilities with ssvc framework","with","triage and prioritize","CISA","vulnerability-management","risk-management","cvss","remediation","vulnerability","prioritization","decision-tree","prioritize","decision","priorities","actionable","tree",{"skillNo":177,"name":178,"nameZh":6,"description":179,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":180,"categories":181,"keywords":182,"publishedAt":39},"01M6HPF6JS9X72WP59094H3ASQ","triaging-security-incident","Performs initial triage of security incidents to determine severity, scope, and required response actions using the NIST SP 800-61r3 and SANS PICERL frameworks. Classifies incidents by type, assigns priority based on business impact, and routes...","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftriaging-security-incident\u002FSKILL.md",[],[183,184,147,34,185,186,187,143,144,188,189,190,191,192,193,194,195,196,197,198],"security","triaging security incident","actions","soc","NIST","analysis","severity-classification","incident-triage","SANS-PICERL","SOC-operations","picerl","conversion","isolation","scope","impact","consistency",{"skillNo":200,"name":201,"nameZh":6,"description":202,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":203,"categories":204,"keywords":205,"publishedAt":39},"01M6HPF2EX6ZYNYYHKBRJN7GEF","triaging-security-incident-with-ir-playbook","Classify and prioritize security incidents using structured IR playbooks to determine severity, assign response teams, and initiate appropriate response procedures.","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftriaging-security-incident-with-ir-playbook\u002FSKILL.md",[],[183,206,207,184,147,161,34,208,186,140,209,210,143,144,211,189,171,212,213,214],"playbook","triaging security incident with ir playbook","teams","IR-playbook","severity","classification","classify","incidents","initiate",{"skillNo":216,"name":217,"nameZh":6,"description":218,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":219,"categories":220,"keywords":221,"publishedAt":39},"01M6HPEY9XPGE7X95AG4XJFQAW","triaging-security-alerts-in-splunk","Triages security alerts in Splunk Enterprise Security by classifying severity, investigating notable events, correlating related telemetry, and making escalation or closure decisions using SPL queries and the Incident Review dashboard. Use when...","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftriaging-security-alerts-in-splunk\u002FSKILL.md",[],[183,222,223,224,225,226,34,227,228,229,186,230,143,231,232,233,192,32,147,234],"security alerts","splunk","triaging security alerts in splunk","alerts","review","siem","dashboard","search","correlation-search","t1566","notable-events","incident-review","de",{"skillNo":236,"name":237,"nameZh":6,"description":238,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":239,"categories":240,"keywords":241,"publishedAt":39},"01M6HPET6XGEPEJPN7V032JGZ0","tracking-threat-actor-infrastructure","Threat actor infrastructure tracking involves monitoring and mapping adversary-controlled assets including command-and-control (C2) servers, phishing domains, exploit kit hosts, bulletproof hosting, a","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftracking-threat-actor-infrastructure\u002FSKILL.md",[],[242,243,244,245,34,246,247,248,249,250,251,231,252,253,32,254,234,255,256,257],"infrastructure","tracking threat actor infrastructure","tracking","threat","monitoring","mitre-attack","threat-actor","threat-intelligence","command-and-control","dns","command","exploit","intelligence","domains","kit","hosts"]