PAGES
← all tools
◆ Exploitation & C2

msfpc

v1.4 open-source

Wrapper around msfvenom that generates basic Meterpreter payloads for multiple platforms with minimal user input.

source ↗ rss ↗ What is a cyber toolchain?

Summary

msfpc is an open-source command-line wrapper that generates Meterpreter and other payloads by driving msfvenom, part of the Metasploit framework, and it costs nothing to use. It runs as a shell script invoked with a single argument, such as a platform name or file extension, and it handles IP selection, staged versus stageless choices, and batch or loop generation across many payload types so the user doesn't have to remember msfvenom's full syntax. It requires msfvenom already installed to function. It is built for penetration testers and red teamers already working inside a Metasploit-based engagement, packaged directly into Kali Linux for that audience, and it makes no attempt to evade antivirus. Its history shows steady releases since 2015 from a small team of four contributors, though there have been no commits in the past year.

Wrapper around msfvenom that generates basic Meterpreter payloads for multiple platforms with minimal user input.

How msfpc helps

Which payload and platform combination do I actually need for this engagement?

takes a single platform name or file extension and resolves it into the full msfvenom command, choosing the matching architecture and Meterpreter type without the user having to know msfvenom's syntax

Which IP should I bake into the payload when I have several interfaces or no fixed one?

accepts an interface name or a keyword for the external address, resolving it to a concrete IP at generation time instead of making the user look it up first

How do I generate every payload of one particular kind, like all staged or all command-shell variants?

filters the same batch generation down to a named subset, so only the payloads matching that category get produced

Can I still get a payload built if I don't know which flags msfvenom needs for staged versus stageless or bind versus reverse?

accepts these as arguments in any order or format and fills in the rest, falling back to sensible defaults when they're left out

What listener setup do I need once the payload is generated?

produces the matching msfconsole resource file or command alongside the payload, ready to load directly into the framework

Languages

Not documented

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface
  6. Community health
  7. Contributor trend distinct committers, this year against last
  8. Maintainer concentration bus factor now against a year ago
  9. Issue backlog trend issues closed per issue opened, 12 months
  10. Responsiveness median time to a maintainer’s first reply

Nine scores for msfpc, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.

Score cards are part of every paid plan.

See plans →

Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.

How this is scored
  • Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
  • Documentation quality — the release-notes rubric published on the analytics page, unchanged.
  • Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
  • Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
  • Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
  • Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
  • Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
  • Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.

Release-note detail over time

See how much detail msfpc puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.

Checking release-note history…

Explore the full chart →

Releases

3 entries

  1. December 20151
  3. July 20152

    3 entries

    1. v1.4 Dec 3, 2015 · release notes

      msfpc v1.4 adds .dll payload support for Windows reverse shells

      └──▷ GET THIS VERSION 
      $ git clone --branch v1.4 https://github.com/g0tmi1k/msfpc.git
# already have the repo? check out this version:
$ git checkout v1.4
    2. v1.3 Jul 20, 2015 · release notes

      msfpc v1.3 adds Bind/Reverse direction selection, tcp/http/https/methods, external IP detection, and verbose file stats.

      └──▷ GET THIS VERSION 
      $ git clone --branch v1.3 https://github.com/g0tmi1k/msfpc.git
# already have the repo? check out this version:
$ git checkout v1.3
      • Adds --direction flag to select Bind or Reverse listener modes
      • Adds --method flag with support for tcp, http, https, find_port, and allports payloads
      • Enables automatic detection of the host's external/WAN IP address for reverse connections
      • Introduces verbose output showing File stats (md5/sha1/size) and error messages from Metasploit/msfvenom

      4 details in Everything

    3. v1.2 Jul 1, 2015 · release notes

      msfpc v1.2 adds batch/loop output modes, CMD/MSF shell types, stageless support, magic CLI args, and verbose flag

      └──▷ GET THIS VERSION 
      $ git clone --branch v1.2 https://github.com/g0tmi1k/msfpc.git
# already have the repo? check out this version:
$ git checkout v1.2
      • Adds --batch mode to produce all possible payloads with filtering capability
      • Adds --loop mode to generate exactly one of each <TYPE> payload
      • Adds CMD shell type option for command prompt shells
      • Adds MSF shell type option for Meterpreter shells
      • Adds support for stageless payloads alongside existing staged payloads
      +1 more show less
      • Adds magic CLI argument guessing capability via long and short flags

      6 details in Everything

    Project health

    Issue, contributor and maintainer activity in g0tmi1k/msfpc, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.

    1. Contributors 0 ±0 vs prior 12 months
    2. Maintainers 0 +0 joined · −0 left, last 12 months
    3. Bus factor 0 committers behind half the commits
    4. Community-filed not measured of issues opened, last 12 months
    5. Median time to close not measured issues closed, last 12 months
    6. Open backlog 7 of 16 issues ever filed
    1. Issues opened / month 0 · 0 communitymaintainers
    2. Open backlog 7
    3. Contributors / month 0
    4. Commits / month 0
    5. Stars 1,333
    Issue themes, last 12 months not measured

    Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this

    Articles

    1 article · updated Nov 4, 2026

    Where msfpc turns up in what others publish: how-tos, attack reports that name it, and incident write-ups. A row says why it is here and quotes where the article names it; the link goes to the publisher.

    Tutorials & guides 1

    • Comprehensive Guide on MSFPC Hacking Articles
      As you all are aware of MSFvenom-A tool in Kali Linux for generating a payload, is also available as MSFvenom Payload Creator (MSFPC) for generating various “basic” Meterpreter payloads via msfvenom.
      2 more quotes
      Source: //github.com/g0tmi1k/mpc Author: g0tmi1k Syntax msfpc <TYPE> (<DOMAIN/IP>) (<PORT>) (<CMD/MSF>) (<BIND/REVERSE>) (<STAGED/STAGELESS>) (<TCP/HTTP/HTTPS/FIND_PORT>) (<BATCH/LOOP>) (<VERBOSE>) Create a Payload with…
      Basically, the msfpc is designed to reduce the user’s effort in generating payload of various platforms with the different-different format of the file.

    Libraries its release ships

    What its latest release locks, checked against known advisories.

    None of its release's images build from a lockfile we can read.

    Add the badge to your README

    Maintain this project? The badge links readers straight to this page, so they can follow every release here.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    compare.md

      Free the public facts, no sign-in Any paid plan all other sections Researcher & Business pricing history and category rank

      my-toolchain — 0 tools

        Betas, release candidates and previews. Turn it off to see final releases only. It also applies to changes you ask for over MCP when you're signed in.
        browse all tools → score card for your toolchain →
        cyber-toolchain / feedback

        Send us feedback