Binject
inject shared object to an apk
Install:
pip install binject
Usage:
usage: binject [-h] [--arch ARCH] <apk_path> <so_path>
Binject: inject shared object to apk
positional arguments:
<apk_path> path to target apk
<so_path> path to target so
options:
-h, --help show this help message and exit
--arch ARCH target architecture (default: arm64-v8a, options: armeabi-v7a, x86, etc)
Features
- injects loadlibrary() to main activity
- injects internet permissions to AndroidManifest.xml if not present
Metadata
Release files for binject 1.0.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| binject-1.0.2.tar.gz | 3.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| binject-1.0.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 7.5 kB
Release files / binject-1.0.2.tar.gz
| Download URL | binject-1.0.2.tar.gz |
|---|---|
| Size | 3.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
41b3703e287fb0db2d217b117aa3b3930dd7d59a145a7d2742e8fb4156519c1e
|
|
BLAKE2b-256 checksum How to use checksums |
dc6458fd1c07d6eed43a8ee007e8aa24e44d6a331e039d6b2d32eea2b24a46ea
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Dec 19, 2025.
Transparency logRelease files / binject-1.0.2-py3-none-any.whl
| Download URL | binject-1.0.2-py3-none-any.whl |
|---|---|
| Size | 4.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7687bce49b3e7157aac01f17ae2d2f5877da434d4ced10ef2d8fc31855d63266
|
|
BLAKE2b-256 checksum How to use checksums |
7e2d4350595adbdb5f0373d8d3308ce7f66c6bb84ac9b75efd820cf0d14e0d8d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Dec 19, 2025.
Transparency log