phpsploit
v3.2 open-sourceThe section your link pointed to isn't on phpsploit's page any more, so we've brought you to the top.
Full-featured C2 framework which silently persists on webserver with a single-line PHP backdoor - nil0x42/phpsploit
Summary
phpsploit is an open-source post-exploitation framework, free to use, that deploys a polymorphic PHP oneliner as a persistent webshell on a compromised webserver and tunnels commands through HTTP headers. It runs as a Python command-line tool on the attacker's machine, launched interactively to hold a session with the backdoored target; Windows is explicitly unsupported as an attacker platform. It is built for red teamers and penetration testers who need a C2 channel that survives on a webserver without a conventional persistent implant, and it is listed in awesome-pentest and packaged for Kali Linux and BlackArch, situating it among the standard pentest-distro toolset rather than against a single named competitor. Development dates back to 2012 with 13 contributors, but there have been no commits in the past year and the last release was over five years ago, so treat it as dormant rather than actively maintained.
Full-featured C2 framework which silently persists on webserver with a single-line PHP backdoor - nil0x42/phpsploit
How phpsploit helps
Which webservers I compromised still have a shell I can reach after the initial access is gone?
keeps a polymorphic PHP oneliner planted on the target and re-establishes a session by tunneling commands to it over HTTP headers, so the channel survives without a conventional file-based implant sitting on disk
How do I run commands on a backdoored webserver without a normal reverse shell?
opens an interactive session on the attacker's machine that wraps shell commands inside HTTP header traffic to the planted oneliner, so the target only ever sees ordinary-looking web requests
What was actually running on a box at the time I had access to it?
includes plugins that grab process listings and system banners from the compromised host through the same tunneled session, giving a snapshot of what the server was doing
Which cloud credentials were sitting exposed on a server I popped?
runs a plugin that hunts the compromised filesystem for cloud credential files and reports what it finds back through the session
Can I tell from the logs which HTTP requests were my C2 traffic and which were normal visitors?
a built-in command displays the HTTP requests the session has sent, so the operator can review exactly what traffic passed to and from the shell
Languages
Command line
No command matches.
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
Responsiveness median time to a maintainer’s first reply
Nine scores for phpsploit, 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 → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
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 phpsploit 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…
Releases
5 entries
No entries match these filters.
- October 20262
- September 20261
- October 20201
- September 20201
Project health
Issue, contributor and maintainer activity in nil0x42/phpsploit, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 0 ±0 vs prior 12 months
- Maintainers 0 +0 joined · −0 left, last 12 months
- Bus factor 0 committers behind half the commits
- Community-filed 100% of issues opened, last 12 months
- Median time to close 6.7 days first maintainer reply 6.7 days
- Open backlog 26 of 98 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 26
- Contributors / month 0
- Commits / month 0
- Stars 2,493
- other 100%
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
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.
Choose a badge style and copy the code →