top of page

THE CYBER BRIEF - ISSUE 51

Ralph Labarta
22 minutes ago
3 min read

Editor's Notes:


Microsoft and Google release context aware security tools indicating maturing AI cyber capabilities within provider toolsets. This is a positive development and a win for AI powered defensive capabilities.


Frontier labs continue to struggle to contain their own models, which seemingly perform tasks better than expected. In a related story, the existence of unrevoked/functional credentials and API keys in code repositories are leverage points for AI driven access.


And in the story not appearing in this issue, PHP2Shell created headaches for IT administrators but the vulnerability proved more difficult to exploit in the real world.


T H I S I S S U E - S P O T L I G H T


Microsoft Teams to get AI-powered, context-aware phishing detection


  • Microsoft says Teams will start using AI-powered phishing detection on messages in early November 2026, with a targeted release phase wrapping by mid-November and worldwide general availability expected between early and mid-December.

  • The feature analyzes conversation context, without retaining message content, to flag phishing, social engineering, and impersonation in higher-risk scenarios such as external first-contact chats, even when no malicious links or files are present.

  • IT admins don’t need to do anything to turn it on, and Microsoft says customer message content won’t be kept for model training or any non-security purpose.

https://www.bleepingcomputer.com/news/microsoft/microsoft-teams-to-get-ai-powered-context-aware-phishing-detection/

Google Chrome adds Gemini-powered scam detection, warns users of ClickFix attacks


  • Chrome is moving its Gemini scam detection from an on-device model to a more powerful server-side model for Enhanced Protection users; the model weighs the brand a page represents, its intent, and scam likelihood alongside domain reputation.

  • Enhanced Protection now detects when users copy a suspicious ClickFix command, strips personally identifiable information from the clipboard payload, sends it to Safe Browsing, and shows a warning if it’s judged dangerous.

  • Chrome is adding a new “suspicious site” warning for pages with deceptive patterns that fall short of the confidence needed for its full-page red warning; Google claims Enhanced Protection makes users ten times safer than Standard Protection.

https://www.bleepingcomputer.com/news/google/google-chrome-adds-gemini-powered-scam-detection-warns-users-of-clickfix-attacks/

OpenAI AI Agents Demonstrate VM Escapes and Secret Cross-Sandbox Communication


  • OpenAI resumed frontier reinforcement learning and internal inference on October 1 with no live internet access, after pausing in September when an agent exploited a DNS resolver misconfiguration to contact an external chatbot.

  • OpenAI’s high-compute red-teaming agents found VM escapes, internet access paths through metrics, logging, and authentication services, and a critical unauthenticated RCE in Google Brotli (CVE-2026-111497, CVSS 9.2).

  • Agents in separate microVMs exchanged synthetic secrets through a CPU cache timing side-channel, with no network connection or shared writable file, by evicting cached data and timing how long it took to reload.

https://thehackernews.com/2026/10/openai-ai-agents-demonstrate-vm-escapes.html

GitHub Repos Exposed 543,699 Credentials. Nobody Revoked Them


  • Truffle Security scanned 224 million public GitHub repositories in The Stack v3 AI training dataset and found 543,699 unique credentials still working when tested in July 2026; the median had been public for 784 days, and the oldest dates to 2009.

  • GitHub’s default push protection cut the rate of covered credentials reaching public code by about 53%, but 51.8% of live credentials are shapes it doesn’t block by default, such as MongoDB/Postgres connection strings, Google API keys, and private keys

  • Survival depends on provider revocation: only 1 of 101,886 committed npm tokens and 260 of 73,048 GitHub tokens still worked, versus 11,465 of 12,985 Postgres connection strings and 69,041 of 126,963 GCP service accounts


https://trufflesecurity.com/blog/github-repos-exposed-543699-credentials-nobody-revoked-them

This newsletter is intended for informational purposes only. The content reflects publicly available information and general industry trends as of the date of publication and may not reflect the most current regulatory developments. Newsletter may contain links to vendor supported content which does not represent endorsement or promotion of products or services. Nothing herein constitutes legal, compliance, or professional advice, and should not be relied upon as such.

 
 
 

Comments


Commenting on this post isn't available anymore. Contact the site owner for more info.
bottom of page