Return to Threats

New OXLOADER Loader Uses Malicious Google Ads to Deliver CastleStealer

thehackernews.com 2026-06-22 malicious AI use Medium

What Happened

Cybersecurity researchers have disclosed details of a new campaign that delivers CastleStealer by means of a previously unreported malware loader dubbed OXLOADER. According to Elastic Security Labs, the campaign leverages malicious Google Ads as a starting point to distribute the malware. Evidence indicates that the threat actor is likely Russian-speaking and financially motivated, owing to the

Why It Matters

The article describes a malvertising campaign (REF8372) where attackers use malicious Google Ads impersonating Node.js to lure users onto a fake download site, which then serves a Storj-hosted batch script that downloads and executes a new Windows loader called OXLOADER and ultimately delivers the CastleStealer infostealer.[1][2][3][5] Researchers note that OXLOADER uses multiple layers of obfuscation and anti-VM techniques to evade both static detection and sandbox analysis, making it harder for defenders to analyze and block.[2] While the report does not mention AI components directly, CyberSE.AI analysis is that such stealthy, malvertising-driven loaders could later be used to deploy AI-powered tools for automated data theft, account takeover, or abuse of AI-enabled SaaS environments. Organizations using browser-based access to AI agents and cloud services should continuously red-team their environments against drive-by infection chains and malvertising vectors, validating that endpoint, browser, and ad-filtering controls effectively block similar campaigns.

Healthcare Fintech SaaS SMB AI startups

CyberSE Analysis

This signal maps to malicious AI use. Organizations using AI agents, LLM APIs, SaaS integrations, or sensitive data workflows should review whether this class of issue could create unauthorized tool execution, data leakage, weak approval gates, or unmanaged supply-chain exposure.

Recommended Actions

  • Restrict AI agent tool permissions and production write paths.
  • Review sensitive data access across prompts, logs, embeddings, memory, and SaaS integrations.
  • Add human approval workflows for high-impact or state-changing actions.
  • Run prompt injection and indirect prompt injection tests against affected workflows.
  • Document the owner, control gap, and remediation deadline for this risk class.

Source

https://thehackernews.com/2026/06/new-oxloader-loader-uses-malicious.html

Talk to AI CISO