dependency-confusion은(는) 무엇을 하나요?
패키지 매니저 의존성 혼동을 이용한 공급망 테스트: 내부 패키지 이름이 공격자가 제어하는 공개 레지스트리로 해석되어 악성 설치 및 스크립트 실행으로 이어집니다. npm/pip/gem/Maven/Composer/Docker 매니페스트 검토 및 공인된 레드팀 공급망 실무에 사용하세요.
패키지 매니저 의존성 혼동을 이용한 공급망 테스트: 내부 패키지 이름이 공격자가 제어하는 공개 레지스트리로 해석되어 악성 설치 및 스크립트 실행으로 이어집니다. npm/pip/gem/Maven/Composer/Docker 매니페스트 검토 및 공인된 레드팀 공급망 실무에 사용하세요.
이 스킬은 패키지 매니저의 의존성 혼동 취약점을 테스트하는 공급망 보안 도구입니다. 조직 내부 패키지 이름이 공개 레지스트리에 등록되어 있을 때, 공격자가 더 높은 버전의 악성 패키지를 게시하여 개발자의 빌드 과정에서 자동으로 설치되도록 하는 공격 벡터를 탐지합니다. npm, pip, gem, Maven, Composer, Docker 등 다양한 패키지 매니저의 매니페스트 파일을 분석하여 내부 패키지 이름과 동일한 공개 패키지가 존재하는지 확인합니다. 또한 공인된 레드팀이 공급망 공격 시나리오를 안전하게 시뮬레이션할 수 있도록 지원하며, 발견된 취약점에 대한 상세 보고서를 생성합니다.
npx skills add https://github.com/yaklang/hack-skills/tree/main/skills/dependency-confusionInstalled? Explore more 코딩 & 개발 skills: steipete/bluebubbles, steipete/eightctl, steipete/blucli · View all 6 →
패키지 매니저 의존성 혼동을 이용한 공급망 테스트: 내부 패키지 이름이 공격자가 제어하는 공개 레지스트리로 해석되어 악성 설치 및 스크립트 실행으로 이어집니다. npm/pip/gem/Maven/Composer/Docker 매니페스트 검토 및 공인된 레드팀 공급망 실무에 사용하세요.
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.