Fuzzing Android
List Price:
$69.99
| Expected release date is Nov 3rd 2026 |
- Availability: Confirm prior to ordering
- Branding: minimum 50 pieces (add’l costs below)
- Check Freight Rates (branded products only)
Branding Options (v), Availability & Lead Times
- 1-Color Imprint: $2.00 ea.
- Promo-Page Insert: $2.50 ea. (full-color printed, single-sided page)
- Belly-Band Wrap: $2.50 ea. (full-color printed)
- Set-Up Charge: $45 per decoration
- Availability: Product availability changes daily, so please confirm your quantity is available prior to placing an order.
- Branded Products: allow 10 business days from proof approval for production. Branding options may be limited or unavailable based on product design or cover artwork.
- Unbranded Products: allow 3-5 business days for shipping. All Unbranded items receive FREE ground shipping in the US. Inquire for international shipping.
- RETURNS/CANCELLATIONS: All orders, branded or unbranded, are NON-CANCELLABLE and NON-RETURNABLE once a purchase order has been received.
Product Details
Author:
Hamzeh Zawawy, Eugene Rodionov, Xuan Xing, Kris Alder, Cory Barker
Format:
Paperback
Pages:
216
Publisher:
No Starch Press (November 3, 2026)
Imprint:
No Starch Press
Release Date:
November 3, 2026
Language:
English
Audience:
General/trade
ISBN-13:
9781718505292
ISBN-10:
1718505299
Weight:
13oz
Dimensions:
7" x 9.25"
File:
RandomHouse-PRH_Book_Company_PRH_PRT_Onix_delta_active_D20260730T232423_157342976-20260730.xml
Folder:
RandomHouse
List Price:
$69.99
Country of Origin:
United States
Pub Discount:
65
Case Pack:
24
As low as:
$53.89
Publisher Identifier:
P-RH
Discount Code:
A
QuickShip:
Yes
Overview
The operational playbook for fuzzing Android, from Binder services to the Linux kernel, by Google's Android Security Team.
Android is three billion devices of hardened, audited, relentlessly defended code, and fuzzing brings it down anyway. The method is almost crude: bury the system in malformed input and wait for the rare case that cracks something open. A crash is the tell, and behind it is usually a way in.
This is the book from the Google engineers who do that for a living. They've fuzzed Android's Binder IPC, the Pixel modem, GPU drivers, and kernel components, and found root-level vulnerabilities the architecture was supposed to keep out of reach. Now they show you how they work.
Most fuzzing books stop at the concept. This one runs the campaign. You'll target the IPC layer with libFuzzer and AFL++, stand up a reproducible environment across emulators and real devices, instrument native code and system services for coverage, triage and reproduce crashes, and extend Syzkaller to reach new kernel drivers. Just as important, you'll build the judgment that separates a fuzzer that finds bugs from one that only makes noise: which targets are worth your time, when to bypass runtime checks, and how to keep a campaign disciplined instead of chaotic.
No other book covers Android fuzzing from userspace services through the kernel. The existing titles stop at app-layer pentesting or teach general fuzzing with no Android specificity. This is the one written by the people who actually found the bugs.
With a foreword by David Kleidermacher, Google's VP of Platforms Security and Privacy.
For security researchers, OEM security engineers, and bug bounty hunters who target the world's largest mobile platform and want the operational playbook rather than the tour.
Android is three billion devices of hardened, audited, relentlessly defended code, and fuzzing brings it down anyway. The method is almost crude: bury the system in malformed input and wait for the rare case that cracks something open. A crash is the tell, and behind it is usually a way in.
This is the book from the Google engineers who do that for a living. They've fuzzed Android's Binder IPC, the Pixel modem, GPU drivers, and kernel components, and found root-level vulnerabilities the architecture was supposed to keep out of reach. Now they show you how they work.
Most fuzzing books stop at the concept. This one runs the campaign. You'll target the IPC layer with libFuzzer and AFL++, stand up a reproducible environment across emulators and real devices, instrument native code and system services for coverage, triage and reproduce crashes, and extend Syzkaller to reach new kernel drivers. Just as important, you'll build the judgment that separates a fuzzer that finds bugs from one that only makes noise: which targets are worth your time, when to bypass runtime checks, and how to keep a campaign disciplined instead of chaotic.
No other book covers Android fuzzing from userspace services through the kernel. The existing titles stop at app-layer pentesting or teach general fuzzing with no Android specificity. This is the one written by the people who actually found the bugs.
With a foreword by David Kleidermacher, Google's VP of Platforms Security and Privacy.
For security researchers, OEM security engineers, and bug bounty hunters who target the world's largest mobile platform and want the operational playbook rather than the tour.
