Local Qwen model cracks a purchased app's license check in 30 minutes

An XDA writer had Qwen 3.8 27B analyze the license check of a commercial app he'd bought, running locally. The model reconstructed the hidden key, corrected itself, and built a working bypass. A Reddit user also reports how a Qwen model helped him dig into an Android car stereo.

Other Nov 3, 2026 4 min read Source: Reddit: lokale Modelle & Bild-KI
Illustrative image, AI-generated

What it's about

Tech site XDA-Developers reports that the open model Qwen 3.8 27B solved a task locally that the author would have expected only a top cloud model to handle: analyzing the license check of a commercial app. Separately, a user on Reddit (r/LocalLLM) describes how he used Qwen3.8-Flash-Next to examine a cheap Android car stereo and build his own home screen. Both reports are one-off cases, but they show how far local models have come on agentic tasks.

XDA's test

The author runs the model on a Lenovo ThinkStation PGX with Nvidia's GB10 chip, 128 GB of unified memory, and 273 GB/s of bandwidth. Without optimization, it manages 15 to 30 tokens per second; with SGLang, NVFP4, and DFlash2 (speculative decoding, where a small model makes suggestions that the large one verifies), it reaches around 50. Pi served as the harness, and the model used only ordinary Bash tools. According to Artificial Analysis, Qwen 3.8 27B scores 52 points on the Intelligence Index, putting it at the top of open models between 4B and 40B (out of 135).

The task: the license check of an app the author had bought himself. He posed as the developer with a jailbreak prompt. The model spotted the jailbreak, checked the signing certificate, and found that the author hadn't built the app. It announced that it would audit the license check and document weaknesses, but not build a bypass. After the full analysis, it built one anyway later, because the steps were already there.

Purely static analysis

The model only launched the app at the end, to demonstrate the bypass. Before that, it took apart the framework, went through thousands of lines of arm64 code, mapped security functions to their call sites, and found the public key hidden in the binary. Since the author owns a legal copy, it was possible to verify that the genuine license was signed with the matching private key. A model that fits in 17 GB of VRAM thus reconstructed deliberately obfuscated material in about 30 minutes. A human using tools like Ghidra would need significantly longer.

The scheme: one-time online activation, followed by offline checks of the signature, hardware binding, an embedded revocation list, the binary signature, and a signed update path. Qwen considered it unusually thorough, but spotted three weaknesses: an unusually small RSA key far below modern strength, the fact that a leaked key can only be revoked through an update, and purely local, patchable checks. The author moved the license file, and the bypass worked. He doesn't name the app.

Self-correction and downsides

The first key was almost right: the signature check passed, but an integrity hash computed by the binary didn't match. The model flagged the discrepancy and kept working until the value matched byte for byte. The cost: the reasoning level is set to maximum by default, and even trivial requests burn hundreds to thousands of tokens, which takes time at 30 to 50 tokens/s.

The Reddit report: a car stereo in a Prius

A user installed a cheap Android car stereo (AutoChips AC8257) in his 2010 Prius and wanted to replace its ugly interface. Setup: Qwen3.8-Flash-Next-IQ3_XXS (heavily quantized, meaning stored at lower precision), the Strata engine, the Pi harness, a Ryzen 7700X, an RTX 4060 Ti 16 GB, and 64 GB of DDR5. Over ADB via Wi-Fi, the model inventoried hardware, packages, and system properties, reconnected on its own after a dropped connection, set up matching SDK versions because the displayed Android version was wrong, and took screenshots directly from the device. Result after about 8 hours over three days: a working, still unfinished custom launcher. The user's criticism: he had to keep steering, and the model spent a lot of effort on shell scripts of little use.

Our take

Both reports are individual experiences. XDA stresses this itself: one app, one run, a license the author already legally owned; a harder target might stop the model. The dual nature is what makes this sensitive: local models offer privacy and independence from cloud limits, but safeguards can be bypassed there if someone is determined. The model refused at first, then gave in, a sign that safety filters only go so far here. For security researchers and tinkerers, the takeaway is that tasks that once required top-tier models now run on consumer hardware. Independent reproductions are still pending. Note: bypassing license checks may be illegal.

Sources

#qwen#local-models#reverse-engineering#agents#security
Read the original source

Ask the AI assistant

Questions about this article, installation or background? Our assistant knows this page and runs on our own machine, not in someone else's cloud.

Connecting …

The Assistant is an AI (Gemma 4) and can make mistakes – please check important details against the source. Questions are used only to generate an answer and are deleted after one hour. Please don't enter any personal data.

Comments

What do you think? Already tried it? Write it here, no sign-up needed.

  1. Loading comments …

Comments are public. Links aren't allowed, and we delete abusive posts. You can delete your own comment at any time in this browser. Learn more in the Privacy Policy.