Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Comments
5 Signs Your Smartphone Has Been Hacked
Newest First  |  Oldest First  |  Threaded View
rjbarbal
100%
0%
rjbarbal,
User Rank: Apprentice
11/4/2016 | 12:51:02 PM
What to do next
Giving the signs of a hacked smartphone is useful for recognition, but including advice on what to do next to recover would be even better.  So, what to do next?  Here are some ideas on what to do if you suspect that your phone or other mobile device is infected:
  • install and run mobile anti-malware software (preferably from more than one vendor)
  • remove any apps that you don't recognize
  • consider wiping the device, restoring factory settings, and reinstalling apps from trusted appstores
  • use mobile security software on your device going forward
  • consider showing the device to a professional, especially if you think it might have been rooted
  • seek the cause of the infection, if possible, and take training on preventing future incidents
  • work with your incident response team to determine the extent of any breach of confidential data and how to respond
  • be more careful in the future

 
prostarjackets
0%
100%
prostarjackets,
User Rank: Apprentice
11/3/2016 | 3:49:06 AM
hi
The creative writing has inspired me a lot. I hope to see the same effort in the future too.

 
newamericanjackets at the walking dead jacket

I read the whole article by the author and I must say it is very nice. Thank for your sharing.
JamesF695
50%
50%
JamesF695,
User Rank: Apprentice
10/30/2016 | 2:22:07 PM
Thanks!
This was useful and informative


Firms Improve Threat Detection but Face Increasingly Disruptive Attacks
Robert Lemos, Contributing Writer,  2/20/2020
Ransomware Damage Hit $11.5B in 2019
Dark Reading Staff 2/20/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
6 Emerging Cyber Threats That Enterprises Face in 2020
This Tech Digest gives an in-depth look at six emerging cyber threats that enterprises could face in 2020. Download your copy today!
Flash Poll
How Enterprises Are Developing and Maintaining Secure Applications
How Enterprises Are Developing and Maintaining Secure Applications
The concept of application security is well known, but application security testing and remediation processes remain unbalanced. Most organizations are confident in their approach to AppSec, although others seem to have no approach at all. Read this report to find out more.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-19668
PUBLISHED: 2020-02-27
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2018-17963. Reason: This candidate is a reservation duplicate of CVE-2018-17963. Notes: All CVE users should reference CVE-2018-17963 instead of this candidate. All references and descriptions in this candidate have been removed to preve...
CVE-2019-12882
PUBLISHED: 2020-02-27
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none.
CVE-2017-6363
PUBLISHED: 2020-02-27
** DISPUTED ** In the GD Graphics Library (aka LibGD) through 2.2.5, there is a heap-based buffer over-read in tiffWriter in gd_tiff.c. NOTE: the vendor says "In my opinion this issue should not have a CVE, since the GD and GD2 formats are documented to be 'obsolete, and should only be used for...
CVE-2017-6371
PUBLISHED: 2020-02-27
Synchronet BBS 3.16c for Windows allows remote attackers to cause a denial of service (service crash) via a long string in the HTTP Referer header.
CVE-2017-5861
PUBLISHED: 2020-02-27
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2017-1000020. Reason: This candidate is a reservation duplicate of CVE-2017-1000020. Notes: All CVE users should reference CVE-2017-1000020 instead of this candidate. All references and descriptions in this candidate have been removed to...