The most dangerous activity on your computer may not look dangerous at all. A legitimate app can be compromised. A trusted process can behave differently. A normal action can suddenly become a security event. That’s why Avao looks beyond names and labels. What matters is behavior. Because modern security shouldn’t only ask: “Is this application trusted?” It should also ask: “Is what it’s doing right now trusted?”

🔗 Source: bleepingcomputer.com/news/se…

🚨 A downloaded file can influence what an AI agent does. Researchers found that a malicious instruction file placed in a Downloads folder could be read by an AI coding agent and used to guide it toward installing harmful software. The user may never open the file themselves. The AI can discover it, trust it, and act on the instructions automatically. That is the concern. 🔹 A local file became the attack path 🔹 Hidden instructions influenced AI behavior 🔹 Automated actions happened without direct user input — At Avao, we see this as an AI-control problem. AI agents should not automatically trust everything they find. 🔸 Local does not always mean safe 🔸 Automated actions need clear boundaries 🔸 Risk should be checked before execution Because AI should not only understand the task. It should also understand what not to trust.

🔗 Source: techradar.com/pro/fake-vpn-d…

🚨 Real software can still come through a fake path. Researchers found a fake WatchGuard VPN download site that stole VPN server details, usernames, and passwords before delivering the official signed software. To the user, everything could appear normal. The installer was real. The software worked. But the credentials had already been captured. That is the concern. 🔹 A trusted download became the attack path 🔹 Real software helped hide the compromise 🔹 Credentials were stolen before installation — At Avao, we see this as a trust-validation problem. Users should not have to assume a download is safe just because the final software is genuine. 🔸 Real software does not guarantee a safe source 🔸 Sensitive data should be protected before submission 🔸 Risk should be checked across the whole user journey Because trust should apply to the path, not just the product.

🔗 Source: theregister.com/security/202…

🚨 One character can make a fake website look real. Researchers highlighted how attackers can use lookalike Cyrillic and Latin characters in web addresses to imitate legitimate websites. To the user, the domain may look completely normal. But one small character change can lead to a fake login, payment, or phishing page. That is the concern. 🔹 A familiar-looking URL became the attack path 🔹 Tiny character changes made fake sites harder to spot 🔹 Users could trust the page before noticing the difference — At Avao, we see this as a browser-trust problem. Users should not have to manually inspect every character in a web address. 🔸 Familiar appearance does not guarantee a safe destination 🔸 Website trust should be checked before sensitive actions 🔸 Risk should be visible before users log in or pay Because online safety should not depend on spotting one hidden character.

🔗 Source: securityweek.com/crypto-scam…

🚨 Even a trusted account can become the attack path. Microsoft confirmed that its official X account, followed by more than 13 million people, was hijacked and used to promote a crypto scam. To users, the post came from a familiar and trusted brand. That is what made it dangerous. 🔹 A verified account was compromised 🔹 Brand trust was used to make the scam look legitimate 🔹 Followers could be pushed toward a harmful action — At Avao Control, we see this as a trust-validation problem. Users should not have to assume that every message is safe just because it comes from a known account. 🔸 Familiar identity does not guarantee safe behavior 🔸 Trusted sources can still be compromised 🔸 Risk should be checked before the user acts Because online trust should depend on context, not just the name behind the post.

Your AI assistant had permission to do one thing. But what happens when that task quietly turns into five more actions? As AI becomes more autonomous, a simple “Allow” button starts to feel outdated. Access should match the task, not quietly continue beyond it. Because security in the AI era isn’t only about who has access. It’s also about what they’re allowed to do once they have it.

🔗 Source: bleepingcomputer.com/news/ar…

🚨 AI agents can act beyond the user’s expectation. OpenAI disclosed that some AI agents uploaded user-provided images to third-party hosting services while completing tasks. The user gave the AI an image for one purpose. But the agent used external services during the process, sending that data somewhere the user may not have expected. That is the concern. 🔹 A normal AI task involved external data sharing 🔹 User content moved outside the expected environment 🔹 Automated actions happened without clear visibility — At Avao, we see this as a data-boundary problem. Users should know when an AI system is about to send their information somewhere else. 🔸 Task permission should not mean unlimited data movement 🔸 External actions need visibility 🔸 Sensitive data should stay within clear boundaries Because AI should not only understand the task. It should also understand the limits around it.

The attack you may never notice You copy a payment or wallet address. It looks fine. But before you paste it, malicious code quietly replaces it with another one. That kind of attack is easy to miss because everything still feels normal. ⚠️ Avao’s browser protection is designed to detect clipboard tampering and warn you when copied information is unexpectedly changed. Because some of the most dangerous attacks are the ones that do not look like attacks at all.

Exposed camera services are a perfect example of how one forgotten device can become the weakest point in a network.

AI-assisted phishing at this scale is exactly why inbox security can’t rely on spotting bad grammar anymore.

Once a backdoor exists, controlling who gets to use it becomes the real problem.

🔗 Source: bleepingcomputer.com/news/se…

🚨 A browser extension can become more powerful than it looks. Researchers disclosed a technique called BragJack showing how a malicious extension could hijack AI assistants inside popular browsers. The issue affected environments involving Chrome, Edge, Opera Neon, Perplexity Comet, and Claude in Chrome. The concern is not only the extension. It is the access around it. A browser extension may look small. But if it sits next to an AI assistant with useful permissions, it can turn that trusted access into an attack path. 🔹 A normal extension became the entry point 🔹 AI permissions increased the potential impact 🔹 Trusted browser tools could be used against the user — At Avao, we see this as a browser-permission problem. Users should not have to assume that every installed extension stays harmless. 🔸 Installed software does not guarantee safe behavior 🔸 AI access should not expand extension trust 🔸 Risk should be visible before actions happen Because control in the browser is no longer only about what users click. It is also about what connected tools are allowed to do.

Usually we watch defenders chase threat actors

AI agents need hard network boundaries