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 objective was to identify prospective security and privacy problems.

I’ve discussed DeepSeek formerly here.

Additional security and privacy issues about DeepSeek have been raised.

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

The findings detailed in this report are based purely on fixed 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, the existence of such code warrants scrutiny, specifically offered the growing issues around data privacy, monitoring, the prospective misuse of AI-driven applications, and cyber-espionage dynamics 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 the other day also.
– Bespoke file encryption and information obfuscation methods are present, with indicators that they could be utilized to exfiltrate user details.
– The app contains hard-coded public secrets, rather than depending on the user device’s chain of trust.
– UI interaction tracking captures detailed user behavior without clear consent.
– WebView adjustment exists, which might permit the app to gain access to private external internet browser data when links are opened. More details about WebView adjustments is here

Device Fingerprinting & Tracking

A significant part of the analyzed code appears to concentrate on gathering device-specific details, which can be utilized for tracking and fingerprinting.

– The app gathers different unique gadget identifiers, consisting of UDID, Android ID, IMEI, IMSI, and provider details.
– System properties, installed bundles, and root detection systems suggest prospective anti-tampering measures. E.g. probes for the existence of Magisk, a tool that personal privacy supporters and security researchers utilize to root their Android gadgets.
– Geolocation and network profiling are present, indicating potential tracking capabilities and making it possible for or disabling of fingerprinting routines by region.
– Hardcoded device model lists suggest the application may behave in a different way depending on the found 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 (since authorization was not approved), it attempts manufacturer particular extensions to access the very same details.

Potential Malware-Like Behavior

While no conclusive conclusions can be drawn without vibrant analysis, a number of observed habits line up with known spyware and malware patterns:

– The app uses reflection and UI overlays, which might assist in unapproved screen capture or phishing attacks.
– SIM card details, serial numbers, and other device-specific data are aggregated for unidentified purposes.
– The app executes country-based gain access to constraints and “risk-device” detection, suggesting possible security systems.
– The app executes calls to pack Dex modules, where additional code is loaded from files with a.so extension at runtime.
– The.so files themselves turn around and make additional calls to dlopen(), which can be utilized to load additional.so files. This facility is not usually examined by Google Play Protect and other fixed analysis services.
– The.so files can be carried out in native code, such as C++. Making use of native code includes a layer of intricacy to the analysis process and obscures the complete degree of the app’s abilities. Moreover, native code can be leveraged to more quickly intensify benefits, potentially making use of vulnerabilities within the os or gadget hardware.

Remarks

While data collection prevails in modern-day applications for debugging and enhancing user experience, aggressive fingerprinting raises considerable privacy concerns. The DeepSeek app requires users to log in with a valid email, which must currently supply enough authentication. There is no valid reason for archmageriseswiki.com the app to strongly collect and send special device identifiers, IMEI numbers, SIM card details, and other non-resettable system residential or commercial properties.

The level of tracking observed here goes beyond normal analytics practices, potentially making it possible for relentless user tracking and re-identification throughout gadgets. These habits, combined with obfuscation techniques and network communication with third-party tracking services, require a higher level of scrutiny from security researchers and users alike.

The employment of runtime code loading as well as the bundling of native code suggests that the app could permit the release and execution of unreviewed, remotely delivered code. This is a severe prospective attack vector. No evidence in this report is presented that from another location deployed code execution is being done, only that the facility for this appears present.

Additionally, the app’s technique to finding rooted devices appears excessive for an AI chatbot. Root detection is often justified in DRM-protected streaming services, where and material defense are important, wiki.eqoarevival.com or in competitive computer game to prevent unfaithful. However, there is no clear rationale for such stringent steps in an application of this nature, raising further concerns about its intent.

Users and companies thinking about installing DeepSeek should know these prospective dangers. If this application is being utilized within an enterprise or federal government environment, extra vetting and security controls should be imposed before enabling its release on handled devices.

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 investigation is required for conclusive conclusions.