{"name":"Coercer: Test Windows RPC Authentication Coercion","description":"Coercer is a Python tool for assessing and triggering Windows server authentication through vulnerable RPC methods. It supports scan, coerce, and fuzz workflows, with results exportable as JSON, SQLite, or XLSX.","github":"https://github.com/p0dalirius/Coercer","url":"https://osrepos.com/repo/p0dalirius-coercer","source":"osrepos.com","sourceDescription":"This repository profile is provided by osrepos.com, an open source repository discovery platform.","repositoryProfile":"https://osrepos.com/repo/p0dalirius-coercer","generatedFor":"open source discovery and AI-assisted research","markdown":"https://osrepos.com/repo/p0dalirius-coercer.md","json":"https://osrepos.com/repo/p0dalirius-coercer.json","topics":["python","security","cli","networking","rpc","ntlm","smb"],"keywords":["python","security","cli","networking","rpc","ntlm","smb"],"stars":null,"summary":"Coercer is a Python tool for assessing and triggering Windows server authentication through vulnerable RPC methods. It supports scan, coerce, and fuzz workflows, with results exportable as JSON, SQLite, or XLSX.","content":"## Overview\n\nCoercer is a Python tool for testing whether a Windows server can be made to authenticate to an arbitrary machine through Remote Procedure Call (RPC) methods. It helps security researchers and operators identify and exercise these authentication-coercion paths, including in NTLM relay or Responder assessments.\n\nThe tool checks remote SMB pipes and tries known RPC functions. Its scan, coerce, and fuzz modes support assessment, controlled coercion attempts, and RPC research. It can target one machine or a list, and can listen for incoming authentications in scan and fuzz modes.\n\n## Key Features\n\n- Scans remote SMB pipes and tests known RPC coercion methods.\n- Attempts RPC calls that may cause a server to authenticate to a specified machine.\n- Fuzzes RPC methods with varied paths for research.\n- Filters attempts by method, protocol, or pipe name.\n- Targets individual hosts or a target list from a file.\n- Supports a configurable delay and random UNC paths between attempts.\n- Exports scan and fuzz results as SQLite, JSON, or XLSX.\n- Provides a PowerShell installer script for building a Windows binary.\n\n## Use Cases\n\n- Security testers can assess a Windows server's RPC exposure before deciding whether to attempt coercion.\n- Red teams can test whether a server can be induced to authenticate to infrastructure prepared for NTLM relay or Responder.\n- Protocol researchers can fuzz RPC methods and paths to investigate coercion behavior.\n- Administrators can review exported results when assessing authentication exposure across a list of targets.\n\n## Our Take\n\nCoercer is a focused tool for Windows RPC authentication-coercion testing, but its quiet maintenance and highly concentrated contributions merit review before relying on it operationally.\n\n**Good fit if:**\n- You need to assess or research Windows RPC methods that may trigger outbound authentication.\n- Your workflow benefits from scan, coerce, or fuzz modes and machine-readable result exports.\n- You can run a Python 3.7-or-newer tool and meet the obligations of its GPL-2.0 license.\n\n**Look elsewhere if:**\n- You need a project with recent release activity: the latest listed release is from 2023, with no release in over a year.\n- Your adoption process requires steady recent development or issue and pull-request activity; the health data reports no recent commits, issue closures, or merged pull requests.\n- You need a tool unrelated to Windows RPC and SMB authentication testing.\n\n## Project Health\n\n| Signal | Value |\n|---|---|\n| Status | **Quiet**: no commits in the last 90 days and no release in a year |\n| Last commit | 2026-04-24 (6 months ago) |\n| Commits, last 90 days | 0 |\n| Releases, last 12 months | 0 (latest 2.4.3, 2023-10-04) |\n| Contributors | 16 (top contributor: 83% of commits) |\n| Issues closed, last 90 days | 0 |\n| Pull requests merged, last 90 days | 0 |\n| Project age | 4 years |\n\nChecked on 2026-10-25 with the GitHub API.\n\n## Project Facts\n\n- Language: Python\n- License: GPL-2.0\n- Stars: 2.3k\n- Forks: 223\n- Topics: authentication, automatic, call, coerce, fuzzing, ntlm, privilege-escalation, rpc\n- Website: https://podalirius.net/\n- Archived: no\n\n## What You Need\n\nDetected in the repository:\n\n- Python >=3.7 (from pyproject.toml)\n- Automated checks on GitHub Actions\n\n## Getting Started\n\nInstall Coercer from PyPI:\n\n```bash\nsudo python3 -m pip install coercer\n```\n\nSee the [repository README](https://github.com/p0dalirius/Coercer) for usage details and mode-specific documentation.\n\n## License in Plain Words\n\n**GPL-2.0** (strong copyleft).\n\n- Commercial use: yes\n- Modify and redistribute: yes\n- You must keep: the license notice\n- Share your changes: yes, the full source of anything you distribute that includes it, under the GPL\n\nA summary, not legal advice: the LICENSE file is what applies.\n\n## Considerations\n\nThe project is marked quiet, with no commits in the last 90 days and no release in over a year. Although it has multiple contributors, most of the code comes from one person, which may increase dependence on that contributor. The health data also shows no recent issue closures or merged pull requests. Coercer requires Python 3.7 or newer; its GPL-2.0 license should be reviewed against your distribution and usage plans. Its purpose is security testing, so use it only on systems you are authorized to assess.","metrics":{"detailViews":0,"githubClicks":0},"dates":{"published":null,"modified":"2026-10-25T00:20:20.000Z"}}