Open-source project
taamarin/box_for_magisk avatar
taamarin/box_for_magisk

Box for Root: five proxy binaries behind three service scripts

Transparent Proxy for Android(root)

2,524 stars293 forksShellGPL-3.0

At a glance

What is it?
taamarin/box_for_magisk is a shell module for rooted Android that installs clash, sing-box, v2ray, hysteria and xray and puts a transparent proxy in front of them. Its declared homepage is a chat channel, the manager app is downloaded from that same channel, the documentation exists in three languages, and the newest release tag has a commit hash inside its name.
Who is it for?
Box for Root fits someone who already roots an Android phone, wants one module that can front any of five proxy implementations with the same transparent rules, and is comfortable editing shell scripts and an ini file as root. It does not fit someone who wants an app store install or a graphical default, because the interface is three commands and a settings file, and the optional manager app is distributed through a chat channel rather than a store or a release asset.
Can I use it commercially?
Yes, with conditions. GPL-3.0 is a copyleft licence: if you distribute software that includes it, you must release that software's source code under the same licence. Running it internally without distributing it does not trigger that obligation.
Is it still maintained?
Yes. The repository last received commits 34 days ago.
What is it written in?
Mainly Shell, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • taamarin/box_for_magisk2,524 ★ · +1
Star history
Repository2026-09-302026-11-15
taamarin/box_for_magisk2.5k2.5k

1 Stars in the last 46 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

Five proxy implementations, one module, transparent rules

Box for Root is a module for three different root frameworks rather than one: it names Magisk, KernelSU and APatch, and its feature list calls the integration with all three seamless. What it actually installs is a suite of five proxy implementations, clash, sing-box, v2ray, hysteria and xray, and what it adds on top is the part that makes them usable without configuring each one separately: a transparent proxy, so traffic from the device is routed without an app having to know anything about a proxy. The services are managed collectively under one name, and they start automatically after a system boot. The readme is specific about the two ends of that lifecycle: starting takes a few seconds, stopping takes effect immediately. So the module is a supervisor as much as a bundle, and the cost of that design is that it holds root-level hooks into the network stack, which is why its uninstall instructions are three recursive deletes under the data partition rather than a single toggle.

Start and stop are not the same command in reverse

The two commands that matter are given in full, and their asymmetry is the first thing to notice. To start, you run the service script and then enable the firewall rules:

bash
su -c /data/adb/box/scripts/box.service start && su -c /data/adb/box/scripts/box.iptables enable

To stop, the order is reversed, rules first and service second:

bash
su -c /data/adb/box/scripts/box.iptables disable && su -c /data/adb/box/scripts/box.service stop

That ordering is deliberate in both directions, rules off before the service dies so traffic is not pointed at nothing. Three helper scripts sit behind those, and each prints its own verb list when called with no arguments. The service script takes start, stop, restart, status, and two scheduling variants. The firewall script takes enable, disable and renew. And a third tool script takes a longer list that mixes checks, subscription updates, a geosite and geoaddress update, a reload, an all option, and four updaters named for the components they refresh: the kernel, the web interface, a query helper and the curl binary itself. Nothing about that surface is self explanatory, which is why the readme prints the usage strings rather than describing them.

Three directories, and a warning to switch it off before editing

The module's layout is given as three path variables rather than a tree, which is the right level of detail for something that runs from a fixed location on the device. The module directory is under the adb data area, the run directory holds the logs, and the settings live in one ini file at a path the readme repeats in full. Alongside those it drops a warning that is easy to skim: turn the module off before you edit the settings file, or you will be editing configuration underneath a running service, which is how a proxy module ends up with a half applied change. The same care appears in the follow up notes, which say that when you modify any of the core configuration files, the tproxy related settings have to match the definitions in the ini file. That sounds obvious and is not: the firewall script and the ini file hold overlapping information, and nothing enforces that they agree.

The public IP loop, and a log line that names the wrong project

One instruction in the readme is worth quoting to anyone setting this up on a home network, because it describes a failure that looks like a bug. If your device has a public IP address, you can add that address to the internal network list in the firewall script to prevent loopback traffic. In other words, without that line, a device that can be reached from outside may route its own connections back through its own proxy. The readme offers it as something you can do rather than something you must, which leaves the default as the risky one. The logs are in the run directory named at the top, and the sentence about them calls the service by a different three letter initialism than the one used everywhere else, which is a small sign that this section was edited against an earlier name. The final line of that section is the correct posture for the whole project: editing any of these files needs appropriate permissions and deserves validation afterwards.

The manager app and the homepage are the same chat channel

Two distribution details sit side by side and they are the ones most worth knowing. The repository's declared homepage is not a site but a link to a chat channel. And the optional manager application, the small app you can use to manage the module on the device, is downloaded from that same link. So there is no store listing, no signed release asset and no documentation site for the app; there is a channel you join. The readme also handles the module's own side effect here: if you receive a continuous stream of notifications, the instruction is to open the root manager, go to the superuser section, find the module by name and disable its logs and notifications. That is a module asking for root on every invocation, and the notification is the visible cost of granting it. It is a reasonable thing for a root module to need and a reasonable thing for the readme to warn about.

Three languages of docs, a commit hash in a tag, and a named ancestor

The repository's front door is documentation rather than a readme: three index files, one each for Indonesian, English and Chinese. That tells you something about who the project is for. The release history is the other thing worth reading carefully. The newest entry is a pre-release whose tag and title both carry a commit hash in parentheses after the version, which is a way of saying this build came from an unmerged commit rather than a tagged state, and it is a habit borrowed from a certain kind of phone firmware packaging. Beneath it sit two ordinary version tags from the same period. The last recorded push is nearly eleven months after the newest release, so the branch carries work with no release attached. And the credits section names the original module this one grew out of, a different repository's Box for Magisk module, which is the honest way to record a lineage that a rename can otherwise hide.

A bare file named sbfr, a web interface, and an update manifest

The root of the repository is a module package rather than an application, so the file list looks like a packaging recipe. There is a module properties file and a metadata directory, the standard Magisk style entry points for install and uninstall, an action script, a customisation script that runs at install time, a build script, and a shell file that the boot sequence calls, which the uninstall instructions tell you to delete by name. Alongside them sit an update manifest, a web root directory for the browser interface, and the box directory holding the scripts the readme has been referring to all along. One entry resists a guess: a file at the root with no extension and a name that looks like an abbreviation, sitting next to the box directory it presumably relates to. Nothing in the visible documentation explains it. The uninstall path is also worth noting, because it is three explicit recursive deletions, one for the data, one for the boot hook and one for the module directory, run as root after removing the module from the manager app.

Editorial conclusion

Box for Root fits someone who already roots an Android phone, wants one module that can front any of five proxy implementations with the same transparent rules, and is comfortable editing shell scripts and an ini file as root. It does not fit someone who wants an app store install or a graphical default, because the interface is three commands and a settings file, and the optional manager app is distributed through a chat channel rather than a store or a release asset. Before you install it, check four things. Whether your root framework is one of the three it names. Which of the five proxy implementations you will actually configure, since the module ships all of them and the settings file is what chooses. What the tproxy settings have to agree with, since the readme says configurations must match the definitions in the ini file or you get a broken device rather than a broken proxy. And whether you will be editing files under the data partition as root, because that is where the whole module lives and where a mistake persists across reboots.

Frequently asked questions

how to use box for magisk

Install it as a module on a rooted device through Magisk, KernelSU or APatch; the services start automatically after boot. Control them from a terminal as root: start the service and then enable the firewall rules, or do the reverse to stop, and use the three helper scripts for status, subscription updates and component refreshes.

Which proxy tools does Box for Root install?

Five: clash, sing-box, v2ray, hysteria and xray. The module's job is to put a transparent proxy in front of them, and the readme says the tproxy related configuration in the core files has to match the definitions in the settings file.

Where does Box for Root keep its configuration and logs?

The module directory is under the adb data area, the run directory holds the logs, and settings live in a single ini file in the module directory. The readme advises turning the module off before editing the settings file so you are not changing configuration under a running service.

How do I uninstall Box for Root?

Remove the module from the Magisk, KernelSU or APatch manager app, then run three recursive deletes as root: one for the module data directory, one for the boot hook script, and one for the module directory itself.

Is there a manager app for Box for Root?

There is an optional manager app for controlling the module on the device, and it is downloaded from a chat channel link rather than from a store or a release asset. That same channel is the repository's declared homepage.

Official sources

  1. License: GPL-3.0
  2. Project website
  3. README
  4. Releases
  5. taamarin/box_for_magisk on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/taamarin-box-for-magisk.svg)](https://hysenlabs.com/projects/taamarin-box-for-magisk)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/taamarin-box-for-magisk.svg)](https://hysenlabs.com/projects/taamarin-box-for-magisk)

Was this useful?