|
|
|
Retrieving a Stolen iPhone in Under 72 Hours |
Si vous voulez bloquer ce service sur vos fils RSS
Si vous voulez nous contacter ou nous proposer un fil RSS
Menu > Articles de la revue de presse : - l'ensemble [ tous | francophone] - par mots clé [ tous] - par site [ tous] - le tagwall [ voir] - Top bi-hebdo de la revue de presse [ Voir]
Retrieving a Stolen iPhone in Under 72 Hours Par Zen OneLe [2012-02-07] à 01:36:33
Présentation : Image representing iPhone as depicted in Crunc... Image via CrunchBase Within 53 hours I was able to get a stolen iPhone safely into police custody. Here's a rough timeline of the steps I went took to get the phone back to the rightful owner Saturday, 2 4 2012 8 45 AM -- iPhone was lost i.e., stolen . Called stolen iPhone and it rang four times before going to voicemail, suggesting that it was powered on and had reception. Used the Find iPhone app to locate the phone using the Apple ID credentials of the stolen iPhone, but it was unable locate the phone. Using the Find iPhone app, sent lock code to stolen iPhone to ensure that it was locked and required an unlock code to access the phone. Using the Find iPhone app, sent messages with sound to the stolen iPhone stating that the phone was lost and to call - - my Google Voice number . No response. Shortly thereafter the iPhone was powered down by the someone who had possession of the phone. I had the owner of the stolen iPhone change passwords to accounts accessed by the iPhone e.g., Gmail, Dropbox, etc . Opted not to report the phone as stolen with AT T yet since I wanted to be able to continue tracking the phone. Also opted not to remotely wipe the iPhone via the Find iPhone app for the same reason. Sunday, 2 5 2012 10 00 AM -- the iPhone was powered on by someone and the location of the phone was identified. Used both the Find iPhone and Find Friends iPhone apps by Apple to track the location of the phone. Another option was logging into iCloud with the Apple ID and password associated with the stolen iPhone ... which I did. Location of the phone tracked to a residential address. Used Google maps and street view to look at the house. Identified the owner of the house using PropertyShark. Gathered information about the owner using Intelius. Again, sent messages with sound to the stolen iPhone stating that the phone was lost and to call - - my Google Voice number . No response. The phone was powered down by the someone who had possession of the phone roughly five minutes after it was powered on. Checked AT T for any unauthorized calls. There were no unauthorized calls. A police report was submitted online to the police department where the phone was stolen. The police department where the phone was currently located different city than where the phone was stolen would not accept a report directly since the theft occurred in a different city. Monday, 2 6 2012 10 46 AM -- the iPhone was powered on and left on. Using both the Find iPhone and Find Friends apps, the GPS location of the stolen iPhone was the same address as the address that was identified on Sunday. A police report was submitted online to the police department. The location of theft was intentionally left vague, implying that the theft occurred in the city where the phone was currently being tracked to. The police department was willing to accept the incident report. Monday, 2 6 2012 1 04 PM -- Called the records and dispatch departments of the PD from the city where the stolen iPhone was currently located. Gave the incident report tracking number to dispatch. After a lengthy conversation, dispatch agreed to send an officer to the house and that the officer would call me back if I needed to cause the stolen iPhone to make a sound. Monday, 2 6 2012 1 36 PM -- Received a call from the responding officer. The police officer stated that he went to the residential address. The officer stated that the owners of the house were at the residence. The police officer gained possession of the phone. The police officer asked me for the unlock code and some contact data that was on the phone to verify ownership. The officer relayed the convoluted story that the individual who had stolen the iPhone told him. We agreed to check the phone into the police department's chain-of-custody and the stolen iPhone will be picked up by the rightful owner soon. Called the police department from where the phone was stolen, stated that the iPhone was retrieved by another police department, and the case was closed. ... and that's a happy ending. Apple has more information about locating a lost or stolen iPhone here. Related articles NYPD meets FMI Cop nabs iPhone thief in NYC tuaw.com Home invasion suspects caught with iPhone's help tuaw.com Find my iPhone iPad2 in iCloud phobe2phile.wordpress.com
Les mots clés de la revue de presse pour cet article : iphone
Les videos sur SecuObs pour les mots clés : iphone
Les éléments de la revue Twitter pour les mots clé : iphone
Les derniers articles du site "Zen One" :
- The Force Awakens ... on Twitter
- Using Python to Sound Like a Wine Snob
- Sync Oracle Calendar to Google Calendar iCal iPhone
- Where The 'Bleep' Did My Identity Go
- Retrieving a Stolen iPhone in Under 72 Hours
- Koobface Analysis
- DHS Cybersecurity Strategy and New California eCrime Unit
- America the Vulnerable
- New Reader Poll - CISSP Exam
- The Pony in the Dung Heap Joke
Menu > Articles de la revue de presse : - l'ensemble [ tous | francophone] - par mots clé [ tous] - par site [ tous] - le tagwall [ voir] - Top bi-hebdo de la revue de presse [ Voir]
Si vous voulez bloquer ce service sur vos fils RSS :
- avec iptables "iptables -A INPUT -s 88.190.17.190 --dport 80 -j DROP"
- avec ipfw et wipfw "ipfw add deny from 88.190.17.190 to any 80"
- Nous contacter par mail
| Mini-Tagwall des articles publiés sur SecuObs : | | | | sécurité, exploit, windows, attaque, outil, microsoft, réseau, audit, metasploit, vulnérabilité, système, virus, internet, usbsploit, données, source, linux, protocol, présentation, scanne, réseaux, scanner, bluetooth, conférence, reverse, shell, meterpreter, vista, rootkit, détection, mobile, security, malicieux, engineering, téléphone, paquet, trames, https, noyau, utilisant, intel, wishmaster, google, sysun, libre |
| Mini-Tagwall de l'annuaire video : | | | | curit, security, biomet, metasploit, biometric, cking, password, windows, botnet, defcon, tutorial, crypt, xploit, exploit, lockpicking, linux, attack, wireshark, vmware, rootkit, conference, network, shmoocon, backtrack, virus, conficker, elcom, etter, elcomsoft, server, meterpreter, openvpn, ettercap, openbs, iphone, shell, openbsd, iptables, securitytube, deepsec, source, office, systm, openssh, radio |
| Mini-Tagwall des articles de la revue de presse : | | | | security, microsoft, windows, hacker, attack, network, vulnerability, google, exploit, malware, internet, remote, iphone, server, inject, patch, apple, twitter, mobile, virus, ebook, facebook, vulnérabilité, crypt, source, linux, password, intel, research, virtual, phish, access, tutorial, trojan, social, privacy, firefox, adobe, overflow, office, cisco, conficker, botnet, pirate, sécurité |
| Mini-Tagwall des Tweets de la revue Twitter : | | | | security, linux, botnet, attack, metasploit, cisco, defcon, phish, exploit, google, inject, server, firewall, network, twitter, vmware, windows, microsoft, compliance, vulnerability, python, engineering, source, kernel, crypt, social, overflow, nessus, crack, hacker, virus, iphone, patch, virtual, javascript, malware, conficker, pentest, research, email, password, adobe, apache, proxy, backtrack |
|
|
|
|
|
