Mitnick's best tool was a telephone and a plausible voice, which makes the audiobook edition of his memoir a slightly odd object. The publisher's own description gets the point right: hacking, for him, was an old fashioned confidence game that needed guile and deception far more than it needed code, and the technical break-ins at Motorola, Sun Microsystems, and Pacific Bell were the easy part. Persuading a person on the other end of a line to hand over what he wanted was the skill, and this is fourteen hours of him describing exactly how he did it.
Kopec Names the Co-Author This Page Omits
David Kopec, whose four-star response from January 2021 is the most careful piece of writing on this page, identifies the achievement precisely. A memoir about a man who spent most of his life sitting in front of a computer had every reason to be dull or impenetrably technical, and this one is neither. Kopec credits the balance of action, technical detail, and material that has nothing to do with hacking, and credits it to Mitnick together with his co-author.
That co-author is William Simon, and the author credit here omits that name entirely. Kopec supplies it directly, calling the collaboration a testament to both. Collaborative authorship on a memoir is entirely normal and usually disclosed somewhere on a product page, and the omission matters because the readability everyone praises is plausibly the collaborator's contribution as much as the subject's. Anyone deciding whether to trust the prose is entitled to know who actually wrote it, particularly on a memoir whose subject built a career out of being believed.
Kopec also supplies the full title, which this page drops: Ghost in the Wires: My Adventures as the World's Most Wanted Hacker. Those words are doing work. They tell a buyer this is a chase narrative told by a fugitive, not a book about securing a network, and the Security and Encryption tag on this listing points in precisely the wrong direction. Expect a manhunt, a run of false identities, and a string of cities rather than a methodology.
Porter Voices a Man Who Voiced Others
Social engineering is dialogue, and dialogue is what a recording does best. The set pieces here are almost all conversations: a call placed to a phone company office, a story told with total confidence, a small piece of information extracted and then leveraged into a larger one. Heard rather than read, those scenes acquire the tension of a con being run in real time, and you get to notice the exact sentence at which the mark stops asking questions. Watching a defense collapse in dialogue is far more instructive than any list of the techniques involved.
Luis Cerdas Ross, posting on the day this recording appeared in August 2011 and rating it five, brings unusual standing to the assessment. That account describes hosting Mitnick as a keynote speaker at a security conference in Costa Rica in 2003, following the campaign mounted while he was held for years without bail or trial, and finding an earlier published account of the capture too partisan to be trusted. Firsthand context of that kind is rare in any review pool.
The reading falls to Ray Porter rather than to Mitnick, which is worth a moment's thought on a memoir whose entire subject is a man performing other people's identities down a phone line. The book is full of impersonations recounted in the first person. A professional reader delivering another man's impersonations adds a layer the printed edition does not have, and whether that layer helps or distances you is genuinely a matter of taste rather than quality.
Isoapu Suspects Mitnick Rounded Off the Corners
Take his version of the events described here with appropriate salt, and one response here says so more elegantly than I can. Writing in Italian in April 2016, isoapu describes having to keep reminding himself that this is a biography rather than a work of fiction, and suspects Mitnick of rounding off certain corners to make events look better and more spectacular than they actually were. That is the correct posture to bring to this book.
Self-mythologizing is the structural risk of any memoir by a person famous for deception, and Mitnick does not entirely resist it. A 2014 response written from France puts the same objection less kindly, finding the author's self-regard hard to bear while still awarding the book five stars. Both readers finished it and enjoyed it. Neither took the storyteller at his word, and neither should you. Enjoyment and skepticism sit together comfortably here, which is more than can be said for most books written by their own subject.
Ratings deserve scrutiny too. Four are counted while five signed responses sit visibly beneath them, and two of the five were written in languages other than English, one of those devoted largely to the condition, price, and delivery of a parcel rather than to anything between the covers. Strip out what is actually about the writing and the sample becomes very small indeed, on a book that has been in circulation since 2011.
Better for Social Engineering Fans Than Hackers
Security awareness trainers should hear this, because it is the most entertaining demonstration available of why technical controls fail against a confident stranger with a telephone. It also suits listeners with no technical background at all: the pursuit, the aliases, and the cities work as a fugitive narrative whether or not you understand what a phone switch does, and the publisher has pitched the book that way from the beginning, promising intrigue and escape rather than instruction in how any of the intrusions were carried out.
A 2023 note filed from India, top marks, sorts the audience usefully, judging the book better for people interested in social engineering than for hackers proper and noting that it can be finished inside a week. That is the right expectation to carry in. Technical content is present but thin by design, and anyone wanting depth on the exploits themselves will feel the balance tipped away from them well before the halfway mark.
It will frustrate anyone hoping for contrition, and anyone looking for a defensive security manual will finish with a good story and no methodology. What you get instead is a first-person account of the human weaknesses that make every security program leak, delivered by someone who exploited them for years. Listen skeptically, enjoy it thoroughly, and assume the version you are hearing has been polished by the man who lived it.
Does the audiobook credit the co-author William Simon?
The author credit on this page names only Kevin Mitnick, though the book was co-written with William Simon. Since the ease of the writing is the most praised thing about it, and a professional collaborator plausibly supplied a good deal of that, the missing name is worth knowing. Search under both.
Is this audiobook technical enough for security professionals?
Less than the subject suggests. The exploits are described, but the emphasis falls on persuasion, pretexting, and the conversations that preceded any access. Awareness trainers will find it invaluable as illustration. Engineers wanting protocol-level depth will find it thin, since the fugitive narrative takes priority over the methods throughout.
Why does the listing show only four ratings?
Five signed responses are visible beneath a counter reading four, which usually means ratings and reviews are being pooled across sources or editions. Two of them were written in other languages and one concerns a parcel rather than the content, so the sample genuinely assessing the English text is smaller still.
How reliable is the memoir as a record of what happened?
Treat it as advocacy as well as memoir. A man famous for talking people out of information is not a neutral witness to his own case, and competing published accounts of the capture exist. The story is compelling and the perspective is unmistakably interested, which are not in conflict with each other.
