type-juggling 是做什麼的？
PHP 類型混淆與弱比較（==）繞過。適用於身份驗證、HMAC/簽名檢查或令牌驗證使用了寬鬆相等、數值強制轉換或未使用嚴格類型的哈希比較的情況——常見於舊版 PHP 和 CTF 風格的程式碼路徑。
PHP 型別轉換與弱比較（`==`）繞過。在驗證、HMAC/簽章檢查或權杖驗證使用鬆散相等、數值強轉或無嚴格型別之雜湊比較時使用，常見於老舊 PHP 及 CTF 風格的程式路徑。
此技能旨在偵測並繞過 PHP 中的型別轉換與弱比較漏洞，特別是透過 `==` 運算子的鬆散比較。當應用程式在驗證身分、檢查 HMAC/簽章或驗證權杖時使用了鬆散相等（而非嚴格相等 `===`）或數值強制轉換，便可能產生此類弱點，這是老舊 PHP 程式碼以及 CTF（奪旗）挑戰中常見的安全缺失。透過利用 PHP 自動型別轉換的機制，例如將字串 `"0e12345"` 與另一個 `"0e67890"` 比較時兩者皆被視為科學記號表示法的零（0e… 視為浮點數零），因此 `0 == 0` 成立，攻擊者可以繞過預期的檢查邏輯。該技能支援多種開發與安全平台，包含 CLI、IDE 外掛及滲透測試框架。使用時，它會分析目標程式碼或回覆中的比較語句，識別使用 `==` 且涉及可能導致型別混淆的內容，例如以 `md5`、`sha1` 等函式的回傳值進行比較，並提供自動化繞過建議或有效的低權限繞過向量，協助開發者與安全研究人員快速理解風險並進行修補。
npx skills add https://github.com/yaklang/hack-skills/tree/main/skills/type-jugglingInstalled? Explore more 程式設計與開發 skills: steipete/bluebubbles, steipete/eightctl, steipete/blucli · View all 6 →
PHP 類型混淆與弱比較（==）繞過。適用於身份驗證、HMAC/簽名檢查或令牌驗證使用了寬鬆相等、數值強制轉換或未使用嚴格類型的哈希比較的情況——常見於舊版 PHP 和 CTF 風格的程式碼路徑。
This repo contains 20 individual skills — each has its own dedicated page.
401/403 bypass playbook. Use when encountering access-denied responses on admin panels, API endpoints, or restricted paths. Covers path manipulation, HTTP method tampering, header injection, protocol downgrade, and automated bypass tools.
Active Directory ACL abuse playbook. Use when exploiting misconfigured AD permissions including GenericAll, WriteDACL, DCSync rights, shadow credentials, LAPS reading, GPO abuse, and BloodHound-guided attack paths.
AD Certificate Services attack playbook. Use when targeting misconfigured AD CS for privilege escalation via ESC1-ESC13 template abuse, NTLM relay to enrollment, CA officer abuse, and certificate-based persistence.
Kerberos attack playbook for Active Directory. Use when targeting AD authentication via AS-REP roasting, Kerberoasting, golden/silver/diamond tickets, delegation abuse, or pass-the-ticket attacks.
AI/ML security playbook. Use when assessing model supply chain attacks (pickle RCE, poisoned weights), adversarial examples, model poisoning, model stealing, data privacy attacks (membership inference, model inversion), and autonomous agent security risks.
Android pentesting playbook. Use when testing Android applications for SSL pinning bypass, exported component abuse, WebView vulnerabilities, intent redirection, root detection bypass, tapjacking, and backup extraction during authorized mobile security assessments.
Anti-debugging detection and bypass playbook. Use when reversing protected binaries that detect debuggers via ptrace, PEB flags, timing checks, or signal/exception handlers on Linux and Windows.
API authentication and JWT abuse playbook. Use when testing bearer tokens, API keys, claim trust, header spoofing, rate limits, and API auth boundary weaknesses.
API authorization and BOLA testing playbook. Use when APIs expose object identifiers, nested resources, hidden writable fields, or weak function-level authorization.
API reconnaissance and documentation review playbook. Use when discovering endpoints, schemas, versions, OpenAPI specs, hidden docs, and surface area for API testing.
Entry P1 category router for API security. Use when choosing between API recon, authorization, token abuse, and hidden-parameter workflows before any deeper API topic skill.
Arbitrary write to RCE playbook. Use when you have an arbitrary write primitive (from heap exploitation, format string, or OOB write) and need to convert it into code execution by targeting GOT, hooks, _IO_FILE vtable, exit_funcs, TLS_dtor_list, modprobe_path, .fini_array, or C++ vtables.
Authentication bypass testing playbook. Use when assessing login flows, password reset logic, account recovery, MFA bypass, token predictability, brute-force resistance, and session boundary flaws.
Entry P1 category router for authentication and authorization. Use when testing login flows, sessions, object authorization, JWT, OAuth, CORS, CSRF, and enterprise SSO weaknesses before any deeper auth topic skill.
Binary protection bypass playbook. Use when identifying and bypassing ASLR, PIE, NX/DEP, stack canary, RELRO, FORTIFY_SOURCE, CET, and MTE protections in ELF binaries to enable exploitation.
Browser and V8 exploitation playbook. Use when exploiting JavaScript engine vulnerabilities including JIT type confusion, incorrect bounds elimination, and V8 sandbox bypass to achieve renderer RCE and sandbox escape in Chrome/Chromium.
Entry P1 category router for business logic testing. Use when workflow abuse, race conditions, pricing flaws, or multi-step state attacks matter more than parser-level input injection.
Business logic vulnerability playbook. Use when reasoning about workflows, race conditions, price manipulation, coupon abuse, state machines, and multi-step authorization gaps.
Classical cipher analysis playbook. Use when encountering substitution ciphers, Vigenere, transposition, XOR, or encoded text in CTF challenges that requires frequency analysis, Kasiski examination, or known-plaintext cryptanalysis.
Clickjacking playbook. Use when testing whether target pages can be framed, whether X-Frame-Options or CSP frame-ancestors are properly configured, and whether UI redress attacks can trigger sensitive actions.
Send and manage iMessages via BlueBubbles, including attachments, tapbacks, edits, replies, and groups.
Control Eight Sleep pods (status, temperature, alarms, schedules).
BluOS CLI (blu) for discovery, playback, grouping, and volume.
Create, search, and manage Bear notes via grizzly CLI.
Capture frames or clips from RTSP/ONVIF cameras.
Search GIF providers with CLI/TUI, download results, and extract stills/sheets.