Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

Malicious APKs (Android Package Kit files) continue to serve as one of the most persistent and adaptable delivery mechanisms in mobile threat campaigns. Threat actors routinely exploit social engineering and off-market distribution to bypass conventional security controls and capitalize on user trust to steal a variety of data, such as log in credentials.

Most mobile security conversations start with code: vulnerabilities, misconfigurations, tokens, and flaws. But few discussions focus on a critical dimension—location: not where an app is used, but where its data travels. In modern mobile architectures, dozens of services operate behind the scenes. SDKs phone home. APIs call upstream. CDNs redirect without warning. Within this chaos, a single, silent connection to a sanctioned region can escalate into a compliance crisis.

Last week, we hosted the Product Spotlight: Build agents in Tines, and it was a hit. We had so many questions that we couldn’t answer them all live, so we’re continuing the conversation here. Before we jump into the Q+A, here’s a quick recap of the webinar in case you missed it: In this session, Head of Product Stephen O'Brien introduced the AI Agent action and shared how it builds on our ongoing evolution of workflows.

We are working tirelessly on our AI First strategy to better protect both humans and their AI tools. KnowBe4 and its advocates spend a lot of time talking to audiences about AI-enabled threats, and rightly so, as recently covered in dozens of previous posts, including this recent one. This year and next promise to be an explosion of cyber threats better enabled by AI. After years of saying AI attacks would be coming, they are here and will be the way that most cybercrime is committed forevermore.