b374k
open-sourceThe section your link pointed to isn't on b374k's page any more, so we've brought you to the top.
b374k is a single-file PHP shell that enables remote web server management via a browser, including file management, command execution, and database access.
Summary
b374k is an open-source PHP web shell that gives someone browser-based control over a compromised or administered server without needing SSH, FTP, or a control panel. It ships as a single PHP file uploaded to the target server, then accessed through any modern browser, with a separate packer utility to bundle password protection, themes, and modules into that file. Its file manager, command and script execution, database clients, process listing, and bind/reverse shell connect make it a tool for penetration testers and red teamers doing post-exploitation work, though the same features explain why it also turns up on compromised sites. First committed in 2014 with 6 contributors, the project has had no commits in the past year.
b374k is a single-file PHP shell that enables remote web server management via a browser, including file management, command execution, and database access.
How b374k helps
What files live on this server, and can I get one off it or drop one on it?
opens a file manager view over the target's filesystem to view, edit, rename, delete, archive, upload, or download files without needing an FTP client
Which processes are running on this box right now?
lists running processes in a task-manager view so a running server can be inspected without a terminal session
How do I run a command or script on a host I have no shell on?
executes shell commands or scripts in several languages directly from the browser and returns the output inline
Can I reach this database without exposing another port or client tool?
connects to the server's configured DBMS and gives a SQL explorer to browse and query it from the same browser session
How do I turn this browser session into a real shell back to my machine?
opens a bind or reverse shell connection from the target so a normal terminal-based session can take over from there
Can I find a specific file or string across this whole filesystem without knowing the path?
searches file names, file contents, and folders, including by regular expression, across the server
Languages
Command line
| 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 b374k, 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 b374k 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
Nothing shipped since we started watching. Releases and docs updates land here as they happen.
Project health
Issue, contributor and maintainer activity in b374k/b374k, 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 not measured of issues opened, last 12 months
- Median time to close not measured issues closed, last 12 months
- Open backlog 17 of 34 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 17
- Contributors / month 0
- Commits / month 0
- Stars 2,663
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 →