Settings

The package

An Android APK, XAPK or APKS, a Chrome or Edge CRX, a Firefox XPI, or a zip of an unpacked extension. It is read here and never leaves this tab.

Drop the package here or choose it

How it works

Read the package, not the store listing

A store listing is marketing. The package is a statement of fact: it contains the exact list of permissions the system will grant, the exact set of components other applications can reach, and the actual code. Those three things are what the software can do, whatever the description on the page says it does.

The gap between them is where the interesting cases live. A torch that asks for contacts. A keyboard with network access. A browser extension whose listing mentions one site and whose manifest.json asks to read and change data on every site you visit. An extension that was honest for two years, changed hands, and shipped an update with a wider permission set that nobody read because updates install silently.

Everything here happens in the tab. That matters for a package you are suspicious of: uploading a possibly malicious APK to a scanning service is a reasonable thing to do and it is also a thing you may not be allowed to do, with a client's application, a pre-release build, or anything under an agreement.

What is actually read out of an APK

An Android APK is a zip, and its AndroidManifest.xml is not text. It is the binary XML that aapt writes: a string pool, a table of resource ids, and a stream of start and end element chunks. That is decoded here by hand, because nothing on the shelf does it in a browser and the format is small and stable enough to be worth writing.

From it: the permission list, which is what the system will grant; the exported components, which say what other applications on the device can reach without asking you. Then the string tables of the classes*.dex files, which name every class the application links, and that is where an analytics or advertising SDK gives itself away, because it cannot be used without being named. The same tables carry every address the code holds as a constant, so you can see what it is built to talk to.

An XAPK or APKS bundle is a zip of APKs and the base one carries the manifest. A Chrome or Edge extension is a zip behind a CRX header, a Firefox add-on is a plain zip, and both carry a manifest.json that says in readable text what it wants.

Reading the result without frightening yourself

Permissions are claims about capability, not evidence of behaviour. A messaging app legitimately needs contacts, the microphone and the camera, and a photo editor legitimately needs storage. The question is never “is this permission alarming” but “does this permission have an explanation in what the app is for”.

So work from the purpose inwards. Write down what the app claims to do, then read the list and account for each entry. The ones you cannot account for are the finding: READ_SMS in a game, ACCESS_FINE_LOCATION in a calculator, REQUEST_INSTALL_PACKAGES in almost anything. For an extension, <all_urls> and webRequest together mean it can read and alter every page you load, including your bank.

The named SDKs and the hardcoded addresses answer the other half: not what it may do, but who it is in touch with. A free application with four advertising SDKs is not free, and the price is in that list.

Related: X-RAY reads what a file really is, MACROLENS shows the macros inside an Office document, DISARM removes the parts of a document that run, and POLICYLENS reads the privacy policy that is supposed to describe all of this in words.

The guide: What a browser extension can do, before you install it

Questions people ask about MANIFEST

Which files can I give it?

An Android APK, or an XAPK or APKS bundle, in which case it finds the base APK inside. A Chrome or Edge extension as a CRX file, whose signing header it strips to reach the zip. A Firefox add-on as an XPI. A zip of an unpacked extension folder. It also takes a bare AndroidManifest.xml, a bare classes.dex or a bare manifest.json if that is all you have.

Where do I get the file before installing?

For an extension already installed somewhere, the browser keeps its folder on disk and you can zip that. For one you have not installed, the CRX can be fetched from the store’s update address with the extension’s ID, and several sites offer that as a download. An APK comes from the developer, from a mirror, or off a phone that has it with adb pull. An APK from a mirror may not be the one on the store, which is one more reason to read it first.

How does it read AndroidManifest.xml when it is not text?

A built APK carries the manifest as binary XML: a pool of strings, a table of attribute ids and a stream of start and end element chunks. This page decodes that format itself, by hand, and reads the package, the versions, every uses-permission, and each activity, service, receiver and provider with its intent filters. When a packer has blanked the attribute names it falls back to the ids, which the system uses anyway.

How does it find tracker SDKs?

Every class an app links is named in the string tables of its classes.dex files, and an SDK’s classes live under its vendor’s package: com.appsflyer, io.sentry and so on. The page reads every string in every dex file and matches the class names against a list of about fifty analytics, crash-reporting and advertising SDKs it knows. An SDK whose classes were renamed by an obfuscator is not found this way, though its addresses often still are. An absence is not proof of absence.

Does an address in the list mean the app talks to it?

It means the address is written into the code as a constant. Some of those are used every time the app runs, some are in a library the app never calls, and some are links in a licence notice. Addresses built up from pieces at runtime are not seen at all. The namespace and licence addresses that every Android build carries, such as schemas.android.com, are left out. Addresses that belong to a known analytics or advertising service are marked.

What does exported mean?

An exported activity, service, receiver or provider can be started or reached by other apps on the device, not only by its own. That is normal for a main screen or a share target, and worth a look for a service or a receiver with no permission guarding it. The page lists the exported ones, the permission that guards each if there is one, and whether it was declared exported or is exported because it has an intent filter.

What is a remote-code hint?

A place in an extension’s scripts where code could arrive from outside the package: a call to eval, a function built from text, a string run on a timer, a script element made at runtime, a script named on another site, or WebAssembly this page cannot read. Bundled libraries carry some of these innocently. A hint says where to read, not what you will find.

Is anything uploaded?

No. The package is unzipped and read in this tab, on your machine, in a background thread so the page stays usable while a large game is read. The only thing fetched is this site’s own copy of the zip library. The page works with the network switched off once it has loaded.

Doing this often? The OBSCURA Sovereign Suite lists what your software is made of, layer by layer, and what each dependency brings with it. On its own, US$2 a month; with everything else, US$5 a month or US$48 a year.