1. Hardcoded secrets found
Attack type
Credential exposure
Risk level
Critical
Perplexity AI contains hardcoded secrets, such as API keys, directly within the application’s code. Attackers who decompile the app can easily extract these secrets and misuse them to gain unauthorized access to backend services, potentially leading to data leaks and system compromise.
In 2019, a major security breach affected an enterprise SaaS provider when attackers exploited hardcoded API keys in their mobile application. This allowed unauthorized access to sensitive customer data, exposing millions of records.
How could Perplexity fix it?
- Store sensitive keys securely using environment variables or encrypted vaults.
- Use secure token management systems to rotate API keys regularly.
- Implement proper access control policies to prevent unauthorized access.
2. CORS misconfigurations: Wildcard origin in response headers
Attack type
Cross-Site Request Forgery (CSRF) and data theft
Risk level
High
Perplexity AI’s API responses contain wildcard origins (*), allowing any website to make requests to the app’s backend. This opens the door to malicious websites making unauthorized requests on behalf of users, potentially exposing sensitive data.
A 2022 data breach at a fintech company resulted from a CORS misconfiguration that allowed attackers to hijack user sessions. Malicious websites could send authenticated requests to the company’s backend, extracting financial data without users’ knowledge.
How could Perplexity fix it?
- Restrict CORS origins to trusted domains only.
- Implement proper authentication and token validation to prevent unauthorized access.
- Regularly review API security configurations.
3. SSL pinning not implemented
Attack type
Man-in-the-Middle (MitM) attack
Risk level
Critical
The Perplexity AI app does not implement SSL pinning, making it vulnerable to interception attacks where hackers can spoof secure connections and steal user data.
In 2017, a high-profile mobile banking app suffered from MitM attacks due to a lack of SSL pinning. Hackers intercepted communication between the app and the bank’s servers, enabling them to steal user credentials and transaction data.
How could Perplexity fix it?
- Implement SSL pinning to verify server certificates before establishing a secure connection.
- Enforce HTTPS with HSTS to prevent insecure connections.
- Conduct periodic security testing to identify and fix network vulnerabilities.
4. Bytecode is not obfuscated
Attack type
Reverse engineering & code tampering
Risk level
High
Lack of bytecode obfuscation makes Perplexity’s app logic easy to reverse-engineer, exposing critical code paths and vulnerabilities.
A popular ride-hailing app was reverse-engineered by attackers in 2020, enabling them to create fraudulent versions of the app that bypassed payment systems, resulting in substantial financial losses for the company.
How could Perplexity fix it?
- Utilize readily available tools on the market to obfuscate code and prevent reverse engineering.
5. ADB detection and missing developer options protections
Attack type
Debugging exploitation
Risk level
High
Perplexity does not detect if ADB debugging or developer options are enabled, making it easier for attackers to manipulate the app in a controlled environment.
In 2021, a mobile game was widely hacked when attackers used ADB debugging to modify in-game parameters. This led to fraudulent in-app purchases and significant revenue loss.
How could Perplexity fix it?
- Implement runtime checks to detect debugging tools.
- Enforce security policies to restrict debugging in production environments.
Why should you care?
If you have the Perplexity app on your phone, these security flaws put your personal data at risk right now as:
? Your private information is exposed
Hackers can exploit these vulnerabilities to steal your personal data, including sensitive login credentials.
? Your data could be stolen without your knowledge
Weak security settings make it easier for malicious websites to siphon off your data silently.
? Cybercriminals can spy on your activity
Without robust protections, attackers can intercept your searches and even steal your login details.
? Your phone could be exploited
The app lacks protections against hacking tools, leaving your device vulnerable to remote attacks.
So, what are your safety measures?
✅ Uninstall the app immediately
Removing the Perplexity AI app from your phone is safest until these issues are addressed.
? Use trusted apps
Stick to well-reviewed apps with strong security measures to protect your data.
?️ Keep your device secure
Regularly update your phone’s software and enable security features like Play Protect to detect threats.
Comparing Deepseek vs. Perplexity: A look at AI security trends
Here’s a breakdown of the key vulnerabilities found in both apps. This comparison highlights the areas where both apps share similar flaws and where Perplexity has unique risks, offering a clearer picture of each app’s security posture.
|
Security Issue |
Deepseek Android |
Perplexity Android |
Impact |
|
Hardcoded Secrets |
? Yes |
? Yes |
Data Theft |
|
Data Exposure (CORS Misconfigurations) |
? Yes |
? Yes |
Data Theft |
|
SSL Pinning Not Implemented |
? Yes |
? Yes |
Account Takeover |
|
Bytecode Not Obfuscated |
? Yes |
? Yes |
Reverse Engineering |
|
ADB/Debugging Protections Missing |
? Yes |
? Yes |
Debugging Exploitation |
|
Unsecured Network Configuration |
? Yes |
? Yes |
Man-in-the-Middle (MitM) |
|
No SSL Validation or Certificate Pinning |
? Yes |
? Yes |
Impersonation Attack |
|
Weak Root Detection |
? Yes |
? Yes |
Privilege Escalation |
|
Susceptibility to the StrandHogg Vulnerability |
? Yes |
? Yes |
Phishing & Identity Theft |
|
Exposure to Janus Vulnerability |
? Yes |
? Yes |
APK Modification & Malware Injection |
|
Tapjacking Attacks |
? Yes |
? Yes |
UI Manipulation |
Key takeaways from Perplexity AI’s risk analysis
AI security debt is getting worse.
Perplexity doesn’t just repeat Deepseek’s mistakes—it builds on them.
Every vulnerability we found in Deepseek is also present in Perplexity, plus five additional weaknesses that widen the attack surface. This isn’t just an oversight; it’s a pattern.
AI applications are evolving fast, but their security isn’t keeping up.
Perplexity is an even bigger risk than Deepseek.
With CORS misconfigurations, lack of bytecode obfuscation, and missing debugging protections, Perplexity is even more exposed than Deepseek.
These gaps make it easier for attackers to steal data, reverse-engineer the app, and manipulate its behavior.
If Deepseek was a warning sign, Perplexity is a full-blown security hazard.
Deepseek’s unique weaknesses still matter.
While Perplexity has more vulnerabilities overall, Deepseek has its own set of critical flaws, like unsecured network configurations and exposure to advanced threats like StrandHogg and Janus. These risks make Deepseek a prime target for more sophisticated attacks that can hijack user sessions and inject malware.
The AI security gap is growing.
AI applications are becoming more powerful, but their security flaws are multiplying just as fast.
With both Deepseek and Perplexity failing fundamental security checks, it’s clear that security isn’t a priority in AI development. Until that changes, users will continue to bear the risks.
Appknox expert opinion: Is Perplexity AI safe?

Subho Halder, CEO and Co-Founder, Appknox, thinks:
Our testing highlights critical vulnerabilities in Perplexity AI that expose users to a variety of risks, including data theft, reverse engineering, and exploitation. It’s crucial for the developers to address these issues swiftly.
In the meantime, users should be cautious about using the app, particularly for sensitive activities.
Conclusion: The bigger picture in AI security
As AI applications like Perplexity continue to evolve, so too must our approach to securing them. The vulnerabilities uncovered in our analysis—whether common oversights like hardcoded secrets or more advanced threats like reverse engineering—highlight the pressing need for robust security measures in AI-powered solutions.
While Perplexity AI shares some critical flaws with Deepseek, it also introduces new risks that should not be overlooked.
For developers, this underscores the importance of proactive security practices—implementing SSL pinning, securing API keys, and addressing CORS misconfigurations are just the beginning.
For users, the message is clear: while AI applications bring tremendous value, they must be trusted only when their security is assured. Until these vulnerabilities are addressed, it’s prudent to remain cautious about using apps that expose sensitive data to unnecessary risk.
At Appknox, we are committed to uncovering security risks in AI-driven apps and helping improve the security posture of these emerging technologies. Stay tuned for future posts in this series, where we continue to analyze popular AI applications and their vulnerabilities.
AI security isn’t a future problem—it’s happening now. If you’re navigating these risks or have insights to share, join our LinkedIn group to discuss the latest threats, best practices, and real-world security challenges with industry peers.
Let’s push for a safer AI future—together.