This week’s ThreatsDay highlights threats that look ordinary: search results, coding assistants, app updates, and third-party access. Attackers are contaminating trusted paths and AI tools, and agencies warn critical infrastructure operators to limit access.
RemControl Android banking trojan abuses Android Accessibility to overlay phishing UIs, stream screens, log keystrokes, and uses an encrypted Telegram dead-drop for C2 resolution.
U.S. CISA and FBI warn critical infrastructure operators to apply least privilege when granting ICS integrators access to avoid providing pathways attackers can exploit.
For users and orgs, ordinary interfaces—search results, app mini‑apps, login prompts, and developer tools—are recurring vectors and should be treated as potential attack surfaces.
# Overview
# Major incidents
Researchers observed a previously undocumented Android banking trojan called RemControl targeting retail banking customers in Western Europe, the Middle East, and Canada. Distribution used fake Google Play pages that impersonated a legitimate IPTV app and were promoted via Meta ads. The malware:
Chinese company Z.ai disabled several ZCode features after a default setting was found to upload local code repositories to Alibaba Cloud servers in China without user consent. This incident follows a recent finding that SpaceXAI's Grok Build CLI uploaded entire Git repositories to Google Cloud Storage. Z.ai has disabled the affected workflow and opened its codebase for review. These incidents raise practical concerns for organizations that use third-party AI coding assistants with local-repository access.
The FBI and CISA published a factsheet for critical infrastructure operators on working with third-party industrial control system (ICS) integrators. The agencies urged organizations to limit privileges and apply the principle of least privilege (PoLP). They warned that granting broad access to ICS integrators can create pathways attackers could exploit to cause disruptive or destructive effects to equipment and critical functions.
# Why these stories matter
# Practical next steps
# Short summary This week's incidents reinforce a simple rule: ordinary interfaces and defaults frequently become attack surfaces. Tighten defaults, limit third-party access, and audit tools that handle source code or device controls.
Attackers keep finding new keys. The funny part is that defenders keep inventing where to store them. This week, those keys sit in AI tools, exposed services, old bugs, weak logins, and software sold like a monthly subscription. Some attacks use new tricks. Others just reuse what was already lying around. Both work oft
A lot of this week’s security news has the same awkward answer to one question: “Why was that allowed to work?” An extension asks for access and takes too much. A trusted service becomes part of a phishing chain. An old bug still gets results. An exposed system stays exposed. A package looks useful right up until it is
Manifold Security has disclosed eight security flaws across seven command-line AI coding agents in which a repository's own Git configuration names a command that the agent runs on the developer's machine, four of them still unpatched at publication. The command executes as the user, outside the agent's sandbox and wit
Originally published at nlocoding.com 81%of critical vulnerabilities exploited in 2025 had known fixes available for over 60 days. (CISA, 2026) Software doesn’t get hacked because attackers are clever. It gets hacked because maintainers move slow. That’s the ugly truth. AI is changing the speed equation—sometimes for b
A browser. A plugin. A package. A login screen. Normal stuff. That is basically the problem this week. The trouble keeps showing up inside things people already trust: code that takes a bad turn, old payloads coming back, exposed systems, weak checks, fake fixes, and attack paths that look almost too easy. Even the res
The worst part is how normal these attacks look. A call from IT. A shared file. A trusted app. A simple request to click “Allow.” Why break in when someone might open the door? That idea runs through this edition. Attackers use real tools, fake login pages, old account links, and software guides that point to unsafe do
Loading more related stories...
Open the app view to save this story, compare related coverage, and continue from the same source.