GitLab

I conducted a fixed analysis of DeepSeek, wiki.vst.hs-furtwangen.de a Chinese LLM chatbot, utilizing variation 1.8.0 from the Google Play Store. The goal was to identify possible security and privacy concerns.

I have actually blogged about DeepSeek previously here.

Additional security and privacy concerns about DeepSeek have actually been raised.

See also this analysis by NowSecure of the iPhone version of DeepSeek

The findings detailed in this report are based purely on static analysis. This means that while the code exists within the app, there is no definitive proof that all of it is performed in practice. Nonetheless, elearnportal.science the presence of such code warrants examination, especially offered the growing concerns around data privacy, demo.qkseo.in surveillance, the potential misuse of AI-driven applications, and cyber-espionage characteristics in between worldwide powers.

Key Findings

Suspicious Data Handling & Exfiltration

- Hardcoded URLs direct information to external servers, raising issues about user activity tracking, such as to ByteDance "volce.com" endpoints. NowSecure determines these in the iPhone app yesterday as well.

• Bespoke encryption and information obfuscation approaches exist, with indicators that they might be utilized to exfiltrate user details.
• The app contains hard-coded public secrets, pipewiki.org instead of counting on the user gadget's chain of trust.
• UI interaction tracking catches detailed user behavior wiki.snooze-hotelsoftware.de without clear permission.
• WebView control exists, which might permit the app to gain access to personal external browser information when links are opened. More details about WebView adjustments is here
  
  Device Fingerprinting & Tracking
  
  A considerable portion of the examined code appears to concentrate on event device-specific details, which can be utilized for tracking and fingerprinting.
  
  - The app collects numerous unique device identifiers, consisting of UDID, Android ID, IMEI, IMSI, and carrier details.
• System homes, installed bundles, and root detection mechanisms recommend possible anti-tampering measures. E.g. probes for the presence of Magisk, a tool that personal privacy advocates and security scientists utilize to root their Android gadgets.
• Geolocation and network profiling are present, indicating prospective tracking abilities and allowing or disabling of fingerprinting programs by region.
• Hardcoded device design lists recommend the application may act in a different way depending on the found hardware.
• Multiple vendor-specific services are utilized to draw out extra gadget details. E.g. if it can not figure out the gadget through standard Android SIM lookup (since permission was not granted), it attempts producer particular extensions to access the same details.
  
  Potential Malware-Like Behavior
  
  While no conclusive conclusions can be drawn without vibrant analysis, numerous observed habits align with recognized spyware and malware patterns:
  
  - The app uses reflection and UI overlays, which might assist in unauthorized screen capture or phishing attacks.
• SIM card details, identification numbers, and other device-specific information are aggregated for unidentified purposes.
• The app executes country-based gain access to constraints and "risk-device" detection, recommending possible surveillance systems.
• The app carries out calls to pack Dex modules, where extra code is loaded from files with a.so extension at runtime.
• The.so submits themselves reverse and make extra calls to dlopen(), which can be utilized to fill additional.so files. This facility is not normally checked by Google Play Protect and other static analysis services.
• The.so files can be executed in native code, such as C++. Using native code adds a layer of complexity to the analysis procedure and obscures the complete extent of the app's capabilities. Moreover, native code can be leveraged to more quickly intensify opportunities, possibly making use of vulnerabilities within the os or device hardware.
  
  Remarks
  
  While information collection prevails in modern applications for debugging and enhancing user experience, aggressive fingerprinting raises considerable privacy issues. The DeepSeek app requires users to visit with a valid email, which ought to currently supply adequate authentication. There is no legitimate factor for the app to aggressively collect and send unique gadget identifiers, IMEI numbers, SIM card details, and other non-resettable system residential or commercial properties.
  
  The extent of tracking observed here goes beyond common analytics practices, potentially making it possible for consistent user tracking and re-identification throughout devices. These behaviors, integrated with obfuscation techniques and network interaction with third-party tracking services, require a greater level of examination from security researchers and users alike.
  
  The employment of runtime code loading along with the bundling of native code suggests that the app could allow the deployment and execution of unreviewed, remotely provided code. This is a serious prospective attack vector. No evidence in this report is provided that remotely deployed code execution is being done, only that the facility for this appears present.
  
  Additionally, the app's technique to detecting rooted gadgets appears extreme for an AI chatbot. Root detection is typically justified in DRM-protected streaming services, where security and material defense are crucial, or in competitive video games to avoid unfaithful. However, there is no clear rationale for such stringent steps in an application of this nature, raising additional concerns about its intent.
  
  Users and organizations thinking about setting up DeepSeek needs to be of these potential threats. If this application is being used within a business or government environment, additional vetting and security controls should be implemented before permitting its deployment on managed gadgets.
  
  Disclaimer: The analysis presented in this report is based upon fixed code evaluation and does not suggest that all found functions are actively used. Further investigation is required for definitive conclusions.