Static Analysis of The DeepSeek Android App

I conducted a fixed analysis of DeepSeek, a Chinese LLM chatbot, using version 1.8.0 from the Google Play Store. The goal was to determine possible security and privacy problems.

I’ve written about DeepSeek previously here.

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

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

The findings detailed in this report are based purely on fixed analysis. This implies that while the code exists within the app, there is no conclusive proof that all of it is carried out in practice. Nonetheless, the existence of such code warrants examination, particularly given the growing concerns around information privacy, surveillance, the prospective misuse of AI-driven applications, and cyber-espionage characteristics between international powers.

Key Findings

Suspicious Data Handling & Exfiltration

– Hardcoded URLs direct data to external servers, raising concerns about user activity tracking, such as to ByteDance “volce.com” endpoints. NowSecure recognizes these in the iPhone app yesterday also.
– Bespoke encryption and data obfuscation techniques are present, with indications that they might be utilized to exfiltrate user details.
– The app contains hard-coded public keys, rather than counting on the user device’s chain of trust.
– UI interaction tracking catches detailed user habits without clear consent.
– WebView adjustment exists, which could permit the app to gain access to private external web browser information when links are opened. More details about WebView adjustments is here

Device Fingerprinting & Tracking

A considerable part of the examined code appears to concentrate on gathering device-specific details, valetinowiki.racing which can be used for tracking and fingerprinting.

– The app gathers different unique device identifiers, consisting of UDID, Android ID, IMEI, IMSI, and provider details.
– System homes, set up bundles, and mechanisms suggest prospective anti-tampering steps. E.g. probes for the presence of Magisk, a tool that personal privacy supporters and security scientists utilize to root their Android gadgets.
– Geolocation and network profiling are present, indicating possible tracking capabilities and enabling or disabling of fingerprinting regimes by region.
– Hardcoded device design lists recommend the application might behave differently depending on the discovered hardware.
– Multiple vendor-specific services are used to draw out additional device details. E.g. if it can not identify the device through basic Android SIM lookup (due to the fact that approval was not given), it attempts manufacturer specific extensions to access the same details.

Potential Malware-Like Behavior

While no conclusive conclusions can be drawn without vibrant analysis, wiki.vst.hs-furtwangen.de a number of observed behaviors align with recognized spyware and malware patterns:

– The app utilizes reflection and UI overlays, which could facilitate unapproved screen capture or phishing attacks.
– SIM card details, serial numbers, and other device-specific information are aggregated for unidentified purposes.
– The app carries out country-based gain access to constraints and “risk-device” detection, suggesting possible monitoring systems.
– The app executes calls to load Dex modules, where additional code is loaded from files with a.so extension at runtime.
– The.so submits themselves turn around and make extra calls to dlopen(), which can be utilized to fill additional.so files. This facility is not generally checked by Google Play Protect and other fixed analysis services.
– The.so files can be executed in native code, such as C++. Using native code adds a layer of intricacy to the analysis process and obscures the complete extent of the app’s capabilities. Moreover, native code can be leveraged to more quickly escalate advantages, potentially exploiting vulnerabilities within the os or gadget hardware.

Remarks

While data collection prevails in modern applications for debugging and enhancing user experience, aggressive fingerprinting raises substantial personal privacy concerns. The DeepSeek app needs users to visit with a legitimate email, which must already supply sufficient authentication. There is no valid factor for the app to aggressively gather and transmit distinct gadget identifiers, IMEI numbers, SIM card details, and other non-resettable system properties.

The degree of tracking observed here goes beyond common analytics practices, potentially making it possible for relentless user tracking and re-identification throughout devices. These behaviors, integrated with obfuscation methods and network communication with third-party tracking services, pyra-handheld.com call for a greater level of scrutiny from security scientists and users alike.

The work of runtime code loading as well as the bundling of native code suggests that the app might permit the release and execution of unreviewed, remotely provided code. This is a severe potential attack vector. No proof in this report exists that remotely released code execution is being done, only that the facility for this appears present.

Additionally, the app’s method to detecting rooted gadgets appears excessive for an AI chatbot. Root detection is frequently justified in DRM-protected streaming services, where security and content defense are vital, or in competitive video games to avoid unfaithful. However, there is no clear rationale for utahsyardsale.com such strict steps in an application of this nature, raising more concerns about its intent.

Users and companies considering installing DeepSeek ought to understand these potential risks. If this application is being utilized within a business or government environment, additional vetting and security controls must be enforced before enabling its deployment on handled gadgets.

Disclaimer: The analysis presented in this report is based upon fixed code review and does not indicate that all found functions are actively utilized. Further examination is needed for definitive conclusions.