Tuesday, February 24, 2026

Bring the Fight to the Edge: Turning Time Into an Advantage in OT Security

Why OT Defenses Often Start Too Late

Industrial organizations are facing a growing paradox in cybersecurity. While operational technology (OT) environments are increasingly connected, most security strategies still assume threats will only materialize once attackers reach the plant floor. In reality, attacks that disrupt industrial operations rarely begin in OT environments. They originate upstream, progress over time and frequently exploit the persistent assumption of isolation. This shift fundamentally changes how defenders must think about visibility, detection and response across Information Technology (IT) and OT domains.

Recent joint research by Palo Alto Networks OT Threat Research Lab, Siemens Cybersecurity Lab and the Idaho National Laboratory challenges several long-held assumptions about how OT attacks originate, evolve and can be stopped. By analyzing global OT network telemetry alongside decades of historical incident data, the research shows that defenders often have far more time and visibility than commonly believed — if they know where to look.

This blog explores how focusing on the network edge, predictive threat behavior and an edge-driven OT security operations model can transform time from a liability into a strategic advantage. Our full findings are detailed in our joint whitepaper, “Intelligence-Driven Active Defense: Securing Operational Technology Environments.”

Threats That Disrupt OT Operations Are Rarely OT-Centric

One of the most persistent myths in industrial security is that OT attacks are fundamentally different from IT attacks. While industrial systems do have unique safety and availability requirements, the paths adversaries use to reach them are often familiar.

Across manufacturing, energy and other critical infrastructure incidents, production shutdowns frequently originate from common IT compromises that occur well before attackers ever interact with industrial systems. This boundary — the network edge between IT and OT — is where attackers often expose themselves through anomalous access patterns, protocol misuse or reconnaissance activity.

Understanding this shift reframes OT defense. The question is no longer whether threats will reach OT systems, but whether defenders can detect and disrupt them before they do.

The Edge Is Where Time Still Exists

In some technology contexts, the term “edge” could refer to digital transformation, analytics or industrial IoT architectures. In OT security, however, the edge is best understood as a strategic control point: the network and security layer where external connectivity, IT systems and OT environments converge.

Our joint research shows that this convergence layer plays a far more critical role in OT incidents than commonly assumed. Internet-exposed OT assets continue to expand, with a 332% increase between 2023-2024 in unique, exposed OT devices and services and nearly 20 million OT-related assets observable on the public internet. Exposure increases risk, but it does not equate to successful disruption. In many cases, it instead creates opportunities for earlier detection and more effective defense.

The data reveals a more consistent pattern: approximately 70% of attacks impacting OT operations originate within IT environments. Across incidents, adversaries frequently begin with familiar enterprise-focused techniques such as credential abuse, brute force attempts and exploitation of IT-facing services. They then progress across shared identity systems, remote access pathways and management infrastructure before executing OT-specific actions.This progression is what makes the edge strategically decisive.

Adversaries rarely move directly from initial compromise to operational impact. They must traverse multiple control layers, generating detectable signals through authentication anomalies, session deviations, protocol misuse and reconnaissance activity.

Time exists at the edge because adversaries must cross it. The edge is therefore not simply where networks connect. It is where defenders retain their greatest advantage: the opportunity to detect and disrupt threats before safety-critical OT functions are affected.

But the edge is not only important because attackers must traverse it. Its true strategic value lies in something even more powerful: the remarkable consistency of adversary behavior.

Predictable Adversary Behavior Creates a Window for Defense

Analysis of more than two decades of OT incidents reveals a striking reality: adversaries rarely operate with the randomness often attributed to them.

Across observed incidents, 82.8% of adversary activity occurred during extended precursor phases, long before operational disruption. On average, attackers remained present for approximately 185 days prior to initiating impact-level activity. This extended dwell time fundamentally reshapes the OT security narrative.

In this context, dwell time refers to the period between an adversary’s initial compromise and the point of disruptive or impact-level activity. It captures how long attackers remain active within an environment while conducting reconnaissance, credential abuse, lateral movement and staging activities prior to operational consequences.

OT disruptions are not typically sudden events. They are the result of gradual progression — reconnaissance, credential abuse, lateral movement, staging — all of which produce detectable signals. While adversaries may differ in tooling, targets or intent, the structure of their behavior remains remarkably consistent.

This consistency is what creates a defensive advantage. When early-stage behaviors are observed at the IT–OT edge, defenders are not reacting to an inevitable outcome — they are interrupting a progression already in motion. The implication is critical: exposure does not automatically translate to disruption.

Rather than treating OT defense as a race against impact, organizations can treat it as a problem of earlier detection and intervention. Techniques such as attack-chain analysis and adversary progression modeling can further support this shift by helping defenders anticipate likely attacker pathways. But the central insight remains clear:

Attackers spend far more time preparing than executing disruption. For defenders, this transforms time from a constraint into a strategic asset.

From Passive Monitoring to Active Defense in OT Environments

The extended dwell times and observable precursor behaviors described earlier create a critical opportunity for defenders. Yet many industrial security programs remain heavily focused on asset inventories and passive monitoring alone. While visibility is essential, it is insufficient by itself. Visibility without response capability does not prevent disruption. This is where OT SecOps becomes essential.

OT SecOps (Operational Technology Security Operations) can be understood as the disciplined practice of detecting, analyzing and safely responding to cyber threats in industrial environments. Unlike traditional IT security operations, OT SecOps is designed around operational continuity, safety constraints and process integrity.

Effective OT SecOps evolves through a progressive security maturity model aligned with established industrial security principles, such as IEC 62443 (an internationally recognized framework for securing industrial automation and control systems.):

  • Architectural Defense establishes secure zones, conduits and segmentation, creating the structural foundation for control and containment.
  • Passive Defense provides the telemetry needed to observe abnormal behavior across industrial protocols and network flows.
  • Active Defense builds on this foundation by enabling pre-approved, OT-specific response actions at the edge, before process impact occurs.

Active Defense capabilities can be implemented through multiple operational mechanisms, including structured response playbooks, threat hunting, containment strategies and OT-specific security operations models such as OT Security Operations Center (OT SOC).

The OT SOC provides a coordinated framework for detection, analysis and controlled intervention, transforming architectural stability and passive visibility into operational defense. By aligning telemetry, analytics and response workflows, the OT SOC enables organizations to disrupt adversary progression while preserving operational continuity and safety constraints.

Without architectural controls and passive visibility, OT SecOps cannot function effectively. Without Active Defense, detection remains reactive and late.

IT–OT SOC Convergence Without Compromise

While the OT SOC strengthens Active Defense within industrial environments, it cannot operate in isolation. The same research that highlights extended dwell times and precursor behaviors also shows that a majority of OT-impacting incidents originate within IT environments.

This creates a structural reality for modern security operations: effective defense requires coordination across both domains. IT–OT SOC convergence is often misunderstood as consolidation, replacement or the absorption of OT security into traditional enterprise workflows. In practice, convergence does not imply collapse.

IT–OT SOC convergence maintains clear separation of duties while enabling coordinated detection and response across zones and trust boundaries. IT teams often identify the early indicators of compromise, while OT teams apply operational context and execute domain-appropriate response actions.

This model allows organizations to manage cyber risk holistically without forcing industrial environments into enterprise security frameworks that may overlook critical safety and availability requirements.

The Key: Stopping Threats Early

OT security has often been framed as a problem of isolation — keeping industrial systems separate from external threats. The reality is more complex. As connectivity increases, isolation alone is no longer sufficient, nor is it realistic.

Our research shows that defenders are not as late as they think. Adversaries leave observable traces long before operational impact occurs, and these traces most often surface at the network edge. Time, in this context, becomes a measurable security variable rather than an uncontrollable constraint. Extended attacker dwell times create windows for detection, decision-making and controlled intervention. By combining edge-focused threat intelligence, predictive analysis and an OT-specific security operations model, organizations can turn time into a defensive advantage.

For leaders, this means OT security strategy should focus on where threats can be detected and stopped early, not on how far control systems can be isolated.

“Bring the fight to the edge” is not a slogan — it is a strategic shift. In OT environments, defense is about time, and the edge is where defenders still have it.

Additional Resources



from Unit 42 https://unit42.paloaltonetworks.com/ot-edge-security/
via IFTTT

From the Captain’s Chair: Kristiyan Velkov

Docker Captains are leaders from the developer community that are both experts in their field and are passionate about sharing their Docker knowledge with others. “From the Captain’s Chair” is a blog series where we get a closer look at one Captain to learn more about them and their experiences.

Today we are interviewing Kristiyan Velkov, a Docker Captain and Front-end Tech Lead with over a decade of hands-on experience in web development and DevOps.

Kristiyan builds applications with React, Next.js, Angular, and Vue.js, and designs modern front-end architectures. Over the years, Docker has become a core part of his daily work — used as a practical tool for building, testing, and deploying front-end applications in a predictable way. 

He focuses on production-ready Docker setups for front-end teams, including clean Dockerfiles, multi-stage builds, and CI/CD pipelines that work consistently across environments. His work is grounded in real projects and long-term maintenance, not theoretical examples.

Kristiyan is the author of four technical books, one of which is “Docker for Front-end Developers”. He actively contributes to open-source projects and is the person behind several official Docker guides, including guides for React.js, Node.js, Angular, Vue.js, and related front-end technologies.

Through writing, open source,speaking and mentoring, he helps developers understand Docker better — explaining not just how things work, but why they are done a certain way.

As a Docker Captain, his goal is to help bridge the gap between front-end developers and DevOps teams.

image5

Can you share how you first got involved with Docker?

I first started using Docker because I was tired of making the excuse “it works on my machine”. We didn’t have many DevOps people, and the ones we had didn’t really know the front-end or how the application was supposed to behave. At the same time, I didn’t know Docker. That made communication difficult and problems hard to debug.

As a front-end developer, I initially thought Docker wasn’t something I needed to care about. It felt like a DevOps concern. But setting up projects and making sure they worked the same everywhere kept causing issues. Docker solved that problem and completely changed the way I work.

At first, Docker wasn’t easy to understand. But the more I used it, the more I saw how much simpler things became. My projects started running the same across environments, and that consistency saved time and reduced stress.

Over time, my curiosity grew and I went deeper — learning how to design well-structured, production-ready Dockerfiles, optimize build performance, and integrate Docker into CI/CD pipelines following clear, proven best practices, not just setups that work, but ones that are reliable and maintainable long term.

For me, Docker has never been about trends. I started using it to reduce friction between teams and avoid recurring problems, and it has since become a core part of my daily work.

What inspired you to become a Docker Captain?

What inspired me to become a Docker Captain was the desire to share the real struggles I faced as a front-end developer. When I first started using Docker, I wasn’t looking for recognition or titles — I was just trying to fix the problems that were slowing me down and it was hard to explain to some DevOps developers what and why this should work like that without knowing the DevOps terms. 

I clearly remember how exhausting it was to set up projects and how much time I wasted dealing with environment issues instead of real front-end work. Docker slowly changed the way I approached development and gave me a more reliable way to build and ship applications.

At some point, I realized I wasn’t the only one in this situation. Many front-end developers were avoiding Docker because they believed it was only meant for back-end or DevOps engineers. I wanted to change that perspective and show that Docker can be practical and approachable for front-end developers as well.

That’s also why I wrote the book Docker for Front-end Developers, where I explain Docker from a front-end perspective, using a real React.js application and walking through how to containerize and deploy it to AWS, with practical code examples and clear diagrams. The goal was to make Docker understandable and useful for people who build user-facing applications every day.

I also contributed official Docker guides for React.js, Angular, and Vue.js — not because I had all the answers, but because I remembered how difficult it felt when there was no clear guidance.

For me, becoming a Docker Captain was never about a title. It has always been about sharing what I’ve learned, building a bridge between front-end developers and containerization, and hopefully making someone else’s journey a little easier than mine.

What are some of your personal goals for the next year?

Over the next year, I want to continue writing books. Writing helps me structure my own knowledge, go deeper into the topics I work with, and hopefully make things clearer for other developers as well. I also want to push myself to speak at more conferences. Public speaking doesn’t come naturally to me, but it’s a good way to grow and to share real, hands-on experience with a broader audience and meet amazing people. I plan to keep contributing to open-source projects and maintaining the official Docker guides I’ve written for Angular, Vue.js, and React.js. People actively use these guides, so keeping them accurate and up to date is important to me. Alongside that, I’ll continue writing on my blog and newsletter, sharing practical insights from day-to-day work.

image2

If you weren’t working in tech, what would you be doing instead?

If I weren’t working in tech, I’d probably be a lawyer — I’m a law graduate. Studying law gave me a strong sense of discipline and a structured approach to problem-solving, which I still rely on today. Over time, though, I realized that technology gives me a different kind of fulfillment. It allows me to build things, create practical solutions, and share knowledge in a way that has a direct and visible impact on people. I don’t think anything else would give me the same satisfaction. In tech, I get to solve problems every day, write code, contribute to open-source projects, write books, and share what I’ve learned with the community. That mix of challenge, creativity, and real impact is hard to replace. Law could have been my profession, but technology is where I truly feel at home.

Can you share a memorable story from collaborating with the Docker community?

One of my most memorable experiences with the Docker community was publishing my open-source project frontend-prod-dockerfiles, which provides production-ready Dockerfiles for most of the popular front-end applications. I originally created it to solve a gap I kept seeing: front-end developers didn’t have a clear, reliable reference for well-structured and optimized Dockerfiles.

The response from the community was better than I expected. Developers from all over the world started using it, sharing feedback and suggesting ideas I hadn’t even considered.

That experience was a strong reminder of what makes the Docker community special — openness, collaboration, and a genuine willingness to help each other grow.

The Docker Captains Conference in Turkey (2025) was amazing. It was well organized, inspiring, and full of great energy. I met great people who share the same passion for Docker.

image8 1

What’s your favorite Docker product or feature right now, and why?

Right now, my favorite Docker features are Docker Offload and Docker Model Runner.

Offload is a game-changer because it lets me move heavy builds and GPU workloads to secure cloud resources directly from the same Docker CLI/Desktop flow I already use. I don’t have to change the way I work locally, but I get cloud-scale speed whenever I need it.

Model Runner lets me run open models locally in just minutes. And when I need more power, I can pair it with Offload to scale out to GPUs.

Can you walk us through a tricky technical challenge you solved recently?

A recent challenge I dealt with was reviewing Dockerfiles that had been generated with AI. A lot of developers were starting to use AI in our company, but I noticed some serious problems right away, images that were too large, broken caching, hardcoded environment variables, and containers running as root. It was a good reminder that while AI can help, we still need to carefully review and apply best practices when it comes to security and performance.

What’s one Docker tip you wish every developer knew?

One tip I wish every developer knew is that Docker is for everyone, not just DevOps or back-end developers. Front-end developers can benefit just as much by using Docker to create consistent environments, ship production-ready builds, and collaborate more smoothly with their teams. It’s not just infrastructure , it’s a productivity boost for the whole stack. I saw a racing number of tech jobs required to have such kind of basic knowledge which overall is positive.

If you could containerize any non-technical object in real life, what would it be and why?

If I could containerize any non-technical object, it would be a happy day. I’d package a perfectly joyful day and redeploy it whenever I needed , no wasted hours, no broken routines, just a consistent, repeatable “build” of happiness.

Where can people find you online?

On LinkedIn, x.com and also my website. I regularly write technical articles on Medium and share insights in my newsletter Front-end World. My open-source projects, including production-ready Dockerfiles for front-end frameworks, are available on GitHub.

Rapid Fire Questions

Cats or Dogs?

Both, I love animals.

Morning person or night owl?

Morning person for study, night owl for work.

Favorite comfort food?

Pasta.

One word friends would use to describe you?

Persistent

A hobby you picked up recently?

Hiking, I love nature

image3


from Docker https://ift.tt/NbQYi25
via IFTTT

Debloat Your Windows 11 ISO with Windows-ISO-Debloater: A Technical Guide and Comparison to other tools

Windows 11, while packed with features, comes overloaded with pre-installed apps, telemetry services, and components that can make you systems, especially in virtual environments or on older hardware, very heavy and unnecessary. Even for IT enthusiasts, having a clean Windows 11 ISO has become a struggle.

This bloat can lead to unnecessary resource consumption, privacy concerns, and slower boot times. That’s where tools like the Windows-ISO-Debloater come in handy. It is a simple PowerShell script that automates the process of stripping down a Windows 11 ISO, creating a clean installation ISO which does not carry on that unnecessary stuff. You can then reduce the deployment times, and save time by not “cleaning” your Windows 11 once you install it.

As someone who’s dealt with countless Windows deployments in VMware setups, I’ve seen how debloating can transform a sluggish OS into a responsive one. In this post, I’ll dive into the technical details of using Windows-ISO-Debloater, walk through its setup and customization, and compare it to other popular methods like Tiny11 Builder and FlyOOBE that I wrote about recently here on StarWind blog.

Understanding Windows 11 Bloat and Why Debloat

Windows 11 includes a host of built-in apps and features that many users never touch: games like Candy Crush, media tools like Windows Media Player, and services tied to telemetry and AI. These elements not only inflate the ISO size but also run background processes that eat up CPU, RAM, and disk space. Debloating removes these, resulting in:

  • Faster Installations – A smaller ISOs mean quicker deployment in VMs or physical machines. (You still need Internet connection, and the updates will gest pulled, however you can bypass online account necessity).
  • Improved Privacy – Disabling telemetry reduces data sent to Microsoft.
  • Resource Efficiency – Ideal for low-spec hardware or virtualized environments.
  • Customization – Bypass hardware checks like TPM 2.0 for broader compatibility.

However, debloating isn’t without risks – removing core components can break functionality, so always test in a test VM first.

Tools like Windows-ISO-Debloater make this process scriptable and reversible through edits.

Introducing Windows-ISO-Debloater

Hosted on GitHub, this open-source PowerShell script targets Windows ISOs directly, modifying them before installation. (By running the script, you’ll create a new copy of this ISO so your original ISO will stay unaffected).

It uses built-in Windows tools like DISM (Deployment Image Servicing and Management) to mount, edit, and repackage the image.

Unlike post-install debloaters, it creates a clean slate from the start, which is perfect for mass deployments.

Key Features and Technical Breakdown

The script focuses on automation with customizable arrays for removal:

  • AppX Package Removal – Targets pre-installed apps via patterns in $appxPatternsToRemove. Examples include Spotify, TikTok, and Disney+. It uses Get-AppxProvisionedPackage and Remove-AppxProvisionedPackage cmdlets.
  • Capabilities and Features – Strips optional Windows features like Windows Fax and Scan or language packs using $capabilitiesToRemove and DISM’s /Remove-Capability.
  • System Packages – Removes core components such as OneDrive or Microsoft Edge with $windowsPackagesToRemove and /Remove-Package.
  • Telemetry and Privacy Tweaks – Disables data collection services and UI elements.
  • Driver Integration – Optionally adds drivers (e.g., Intel RAID) from a Drivers/ folder using DISM’s /Add-Driver.
  • ISO Compression and Bypasses – Converts to ESD format for smaller files and skips TPM/hardware checks via registry tweaks in the mounted image.
  • OOBE Customization – Integrates an autounattend.xml file to automate the Out-of-Box Experience (OOBE), enabling user folders or bypassing account setup.

Under the hood, it mounts the ISO with Mount-DiskImage, extracts editions using Get-WindowsEdition, and rebuilds with oscdimg.exe (downloaded from Microsoft if needed) or the experimental IMAPI2FS COM interface.

It’s GPL-3.0 licensed, ensuring you can modify it freely.

Tested on Windows 11 24H2 (build 26100.1742) and Windows 10 22H2, it requires admin privileges and PowerShell. No internet beyond initial tool downloads. (The 25H2 needs Internet access).

Step-by-Step Usage

1. Download and Prepare: Grab the script from GitHub: https://itsnileshhere.github.io/Windows-ISO-Debloater

Have your Windows 11 ISO ready (download from Microsoft).

2. Run Interactively: Execute .\isoDebloaterScript.ps1 as admin. It prompts for ISO path, edition (e.g., Pro), and options like removing Edge or enabling ESD compression.

Windows ISO Debloater script

Windows ISO Debloater script

 

3. Automated Mode: For scripting, use flags: .\isoDebloaterScript.ps1 -noPrompt -isoPath “C:\win11.iso” -winEdition “Pro” -outputISO “C:\debloated.iso” -EDGERemove yes -AIRemove yes -TPMBypass yes.

4. Customize: Edit the script’s arrays to fine-tune removals. For example, add patterns to $appxPatternsToRemove for specific apps.

5. Output and Install: The result is a bootable ISO. Burn to USB with Rufus or mount in VMware for testing.

When you run the script interactively, you are asked few questions about what you want to remove. Example below.

The script asks questions when running interactively

The script asks questions when running interactively

 

Warnings: Back up originals, as modifications are irreversible without re-downloading. IMAPI2FS may fail on some systems.

Note: In my testing I was using a 25H2 ISO and with the debloated ISO, during install, I was able to create a local account (the non-debloated kept logging me in with Second-factor authentication (2FA) directly without giving me option of a simple local account.)

First choose the version of W11 you want to work with

First choose the version of W11 you want to work with

 

Depending of the ISO you pick to load, the script leaves some options as “not found”. This is normal as not all W11 ISOs are equal.

Different options removed or not, depending on the ISO you’re using

Different options removed or not, depending on the ISO you’re using

 

In my tests, a debloated ISO shaved off 1-2GB and booted 20-30% faster in a VM. Also, the number of background processes running after the first boot is about 1/3 less than the original full-blown ISO.

The number of background processes compared

The number of background processes compared

Comparing Other Debloating Methods

While Windows-ISO-Debloater excels at ISO-level tweaks, alternatives vary in scope. Some focus on post-install, others on custom images. Let’s compare key players.

Tiny11 Builder: The Lightweight ISO CreatorTiny11 Builder is another PowerShell script for crafting debloated Windows 11 ISOs.

It removes bloat like Clipchamp, Xbox, and Weather, while keeping the system serviceable for updates and features.

A “Core” variant strips more, including WinSxS (Component Store), disabling updates (not good idea tbh) but ideal for testing VMs.

How It Works: Mounts the ISO, applies removals via DISM, and includes an unattended file for compact deployment and MSA bypass.

Bypasses hardware checks automatically.

Pros vs. Windows-ISO-Debloater:

  • Simpler for beginners: Fewer flags, GUI wrappers available too
  • Deeper core removals (e.g., Defender, Update).
  • Supports any Windows 11 build.

Cons:

  • Less granular: Fixed removal lists, harder to customize without script edits.
  • Core version locks out post-install changes, risking instability.
  • No driver integration or ESD compression out-of-box.

Tiny11 is great for quick, minimal ISOs (e.g., 25H2 builds), but Windows-ISO-Debloater offers more toggles for targeted debloating.

FlyOOBE: Post-Install and Setup Tweaker

FlyOOBE (evolution of Flyby11) focuses on OOBE customization during or after setup, not ISO creation.

It bypasses hardware restrictions, removes AI features (Copilot, Recall), and debloats apps like OneDrive post-install.

Version 2.4 enhances AI detection with RemoveWindowsAI integration.

How It Works: Runs as a toolkit for upgrades or fresh installs, offering interactive OOBE tweaks, privacy settings, and browser installs.

Uses registry edits and PowerShell for removals.

Pros vs. Windows-ISO-Debloater:

  • Handles existing installs: No need to recreate ISOs.
  • AI-specific focus: Strips modern bloat like Slopilot.
  • Upgrades Win10 to 11 seamlessly.

Cons:

  • Not ISO-centric: Changes apply after boot, potentially leaving remnants.
  • Less for bulk deployments; more for individual tweaks.
  • Risks breaking updates if over-debloated.

FlyOOBE complements ISO tools so you can use it for fine-tuning after a debloated install from Windows-ISO-Debloater too.

Other Notable Methods

  • NTLite: GUI-based ISO editor for advanced customization, including component removal and driver integration. More user-friendly than scripts but paid for full features.
  • Winhance or Win11Debloat: Post-install scripts for app removal via PowerShell. Good for quick cleanups but not ISO-focused.
  • Manual PowerShell: Use Get-AppxPackage | Remove-AppxPackage for apps, but time-consuming without automation.

Enterprise Tools and Strategies for Large Organizations

For larger enterprises, debloating and deployment scale up significantly, shifting from scripts to centralized management. Microsoft Intune is a core tool, enabling cloud-based device management, app deployment, and policy enforcement via Endpoint Manager.

Other options include Microsoft Endpoint Configuration Manager (formerly SCCM) for on-premises or hybrid setups, handling task sequences for OS imaging.

Microsoft Deployment Toolkit (MDT) and Windows Deployment Services (WDS) are free for creating and pushing custom images.

Debloating in enterprise often uses Group Policy Objects (GPOs) to disable telemetry, remove apps, and tweak settings across domains.

Intune policies can deploy PowerShell scripts like Win11Debloat for in-place removals.

For master images, enterprises use tools like MDT to build “golden” images with apps and drivers, then deploy via WDS or Autopilot.

Acronis Snap Deploy is indeed used by some for imaging, supporting offline/online creation and multicast deployment to multiple machines, especially in mixed Windows/Linux environments.

Example from the lab. Guess which VM is debloated,

Example from the lab. Guess which VM is debloated,

Final Words

Windows-ISO-Debloater stands out for its balance of automation, customization, and ISO-level efficiency, making it a top choice for IT pros building clean Windows 11 images. Compared to Tiny11’s simplicity or FlyOOBE’s post-setup flexibility, it offers granular control without sacrificing usability.

However, you should always test thoroughly and do not debloat too aggressively as you might lose needed features.

If you’re virtualizing Windows in VMware or Hyper-V, a debloated ISO can save resources and simplify management.



from StarWind Blog https://ift.tt/BzGL30m
via IFTTT

Scaling security operations with Microsoft Defender autonomous defense and expert-led services

Today’s security leaders are operating in an environment of truncated cyberattack timelines with aging defenses built for slower, linear cyberthreats that can no longer keep pace with advanced cyberthreats. AI-powered threat actors now use social engineering and malware that adapt in real time, allowing a single phishing message to escalate into a multidomain compromise within minutes. In many organizations, however, the bigger challenge lies closer to home: Years of accumulated technical debt inside the security operations center (SOC) and best-of-breed security investments have left many teams grappling with stitched together siloed tools, each producing fragments of insight that analysts must manually piece together. They’re also struggling with closing the skills gap and finding the right expertise.

The new e-book, Unlocking Microsoft Defender: A guide to autonomous defense and expert-led security, explores why this model has become unsustainable and how organizations can shift to a more integrated approach to modern defense. Implementing genuine SOC transformation is no easy task, and many organizations seek outside expertise to affect real change. Sign up to download the e-book now and learn more about topics like how autonomous defense paired with human judgment can help organizations tackle today’s toughest cyberthreats, and how adding services from Microsoft Security Experts can help defend against threats, build cyber resilience, and modernize security operations.

WASTED EFFORT: 20% of an analyst’s week—one full workday in five—is lost to manual toil.1

Why autonomous defense is now the standard

To keep pace with this new class of threat actor, security teams need to move beyond incremental automation and fundamentally rethink how defense operates. For years, SOCs have relied on manual triage—analysts chasing large volumes of low confidence alerts across disconnected tools. Security orchestration, automation, and response (SOAR) platforms improved efficiency by automating known responses, but they remain reactive by design, engaging only after an incident has already taken shape. This model struggles when attacks unfold in minutes, not days.

ALERT OVERLOAD: 42% of alerts go uninvestigated simply due to capacity constraints.1

The next evolution is an agentic SOC—one where defense is driven by continuous signal correlation, automated decision making, and human expertise applied where it matters most. Microsoft Defender XDR provides a unified operational layer across domains, closing visibility gaps created by siloed tools and enabling automated disruption of complex attacks before they escalate. By shifting routine investigation and response to AI-powered agents, security teams can reduce response time, contain cyberthreats earlier, and refocus human effort on proactive hunting, strategic analysis, and resilience rather than constant firefighting.

The blueprint for autonomous defense

The shift toward autonomous defense starts with unifying how security operations work. Fragmented tools force teams to interpret cyberthreats one signal at a time, leaving context scattered and response uneven. The guide explores how coordinated defense brings threat signals and protection actions together, revealing patterns that individual alerts may never reveal on their own. Instead of adjudicating noise, teams gain clear attack narratives that support faster, more confident decisions.

A graphic in the shape of a figure eight illustrating the connection between AL-powered defense and human expertise.

Autonomous defense builds on that foundation by using AI to act early in the attack lifecycle—not after damage is done. The e-book examines how modern platforms can contain in-progress threats and anticipate attacker movement, reducing reliance on manual escalation and static response models. The result is a SOC that spends less time reacting to incidents and more time shaping security outcomes—an operating model designed for speed, scale, and the inevitability of attack.

See how Microsoft Security Experts uncover fake remote workers

In the e‑book, we explore how autonomous defense is most effective when paired with human judgment and deep experience managing real incidents. Automated protection serves as the foundational security layer, blocking cyberthreats at machine speed, and reducing operational strain. When cyberattacks evolve or escalate, expert‑led hunting and managed detection and response bring global threat intelligence and real‑world insight to contain incidents and strengthen defenses. Human insights feed back into the platform, continuously improving automated protections and sharpening the organization’s overall security posture. In this video, we share a story of how fake profiles and fabricated identities can sometimes appear all too real.

Turn autonomous defense into resilient security

The e-book includes information about how organizations layer expertise at every stage of modern defense—combining autonomous protection with continuous human insight. Microsoft Security Experts helps in three key ways: with technical advisory to help modernize security operations, managed extended detection and response for around the clock defense against cyberthreats, and incident response and planning to build cyber resilience. The e-book further explains how this model emphasizes earlier threat discovery, reduced noise, and faster, more confident decision‑making as part of day‑to‑day security operations.

Sign up to download the e-book and read about how intelligence‑led incident response and direct access to security advisors can help organizations build long‑term resilience—not just recover from individual incidents. With expert guidance on readiness, response, and platform optimization, security teams can modernize operations, reduce integration overhead, and measurably improve outcomes. The result is a more resilient security program—one that resolves cyberthreats faster, lowers breach risk, consolidates cost, and enables teams to focus on solving meaningful security problems rather than chasing alerts.

Learn more about the Microsoft Defender Experts Suite

As security teams confront faster, more complex cyberattacks—and persistent gaps in skills and capacity—many are looking for practical ways to strengthen defenses without adding operational strain. The Microsoft Defender Experts Suite provides expert‑led security services to help organizations defend against advanced cyberthreats, improve resilience, and modernize security operations. If you’re exploring how to combine autonomous protection with continuous human expertise, read the full announcement for deeper context on what’s new and how these services work together.

Learn more

Learn more about Microsoft Security Experts and Microsoft Defender XDR.

To learn more about Microsoft Security solutions, visit our website. Bookmark the Security blog to keep up with our expert coverage on security matters. Also, follow us on LinkedIn (Microsoft Security) and X (@MSFTSecurity) for the latest news and updates on cybersecurity. 


1Microsoft and Omdia, State of the SOC: Unify Now or Pay Later report, 2026.

The post Scaling security operations with Microsoft Defender autonomous defense and expert-led services appeared first on Microsoft Security Blog.



from Microsoft Security Blog https://ift.tt/la8uW4V
via IFTTT

Lazarus Group Uses Medusa Ransomware in Middle East and U.S. Healthcare Attacks

The North Korea-linked Lazarus Group (aka Diamond Sleet and Pompilus) has been observed using Medusa ransomware in an attack targeting an unnamed entity in the Middle East, according to a new report by the Symantec and Carbon Black Threat Hunter Team.

Broadcom's threat intelligence division said it also identified the same threat actors mounting an unsuccessful attack against a healthcare organization in the U.S. Medusa is a ransomware-as-a-service (RaaS) operation launched by a cybercrime group known as Spearwing in 2023. The group has claimed more than 366 attacks to date.

"Analysis of the Medusa leak site reveals attacks against four healthcare and non-profit organizations in the U.S. since the beginning of November 2025," the company said in a report shared with The Hacker News.

"Victims included a non-profit in the mental health sector and an educational facility for autistic children. It is unknown if all these victims were targeted by North Korean operatives or if other Medusa affiliates were responsible for some of these attacks. The average ransom demand in that period was $260,000."

The use of ransomware by North Korean hacking groups is not without precedent. As far back as 2021, a Lazarus sub-cluster referred to as Andariel (aka Stonefly) was observed striking entities in South Korea, Japan, and the U.S. with bespoke ransomware families like SHATTEREDGLASS and Maui.

Then, in October 2024, the hacking crew was also linked to a Play ransomware attack, marking the transition to an off-the-shelf locker to encrypt victim systems and demand a ransom.

That said, Andariel is not alone in shifting from custom ransomware to an already available variant. Last year, Bitdefender revealed that another North Korean threat actor tracked as Moonstone Sleet, which previously dropped a custom ransomware family called FakePenny, had likely targeted several South Korean financial firms with Qilin ransomware.

These changes possibly signal a tactical shift among North Korean hacking groups where they are operating as affiliates for established RaaS groups rather than developing their tools, the company told The Hacker News.

"The motivation is most likely pragmatism," Dick O'Brien, principal intelligence analyst for the Symantec and Carbon Black Threat Hunter Team, said. "Why go to the trouble of developing your own ransomware payload when you can use a tried-and-tested threat such as Medusa or Qilin? They may have decided that the benefits outweigh the costs in terms of affiliate fees."

The Lazarus Group's Medusa ransomware campaign includes the use of various tools -

  • RP_Proxy, a custom proxy utility
  • Mimikatz, a publicly available credential dumping program
  • Comebacker, a custom backdoor exclusively used by the threat actor
  • InfoHook, an information stealer previously identified as used in conjunction with Comebacker
  • BLINDINGCAN (aka AIRDRY or ZetaNile), a remote access trojan
  • ChromeStealer, a tool for extracting stored passwords from the Chrome browser

The activity has not been tied to any specific Lazarus sub-group, despite the fact that the extortion attacks mirror previous Andariel attacks.

"The switch to Medusa demonstrates that North Korea's rapacious involvement in cybercrime continues unabated," the company said. "North Korean actors appear to have few scruples about targeting organizations in the U.S. While some cybercrime outfits claim to steer clear of targeting healthcare organizations due to the reputational damage it may attract, Lazaurs doesn’t seem to be in any way constrained."



from The Hacker News https://ift.tt/zSj6Nl2
via IFTTT

UnsolicitedBooker Targets Central Asian Telecoms With LuciDoor and MarsSnake Backdoors

The threat activity cluster known as UnsolicitedBooker has been observed targeting telecommunications companies in Kyrgyzstan and Tajikistan, marking a shift from prior attacks aimed at Saudi Arabian entities.

The attacks involve the deployment of two distinct backdoors codenamed LuciDoor and MarsSnake, according to a report published by Positive Technologies last week.

"The group used several unique and rare instruments of Chinese origin," researchers Alexander Badaev and Maxim Shamanov said.

UnsolicitedBooker was first documented by ESET in May 2025, attributing the China-aligned threat actor to a cyber attack targeting an unnamed international organization in Saudi Arabia with a backdoor dubbed MarsSnake. The group is assessed to be active since at least March 2023 and has a history of targeting organizations in Asia, Africa, and the Middle East.

Further analysis of the threat actor has uncovered tactical overlaps with two other clusters, including Space Pirates and an as-yet-unattributed campaign targeting Saudi Arabia with another backdoor referred to as Zardoor.

The latest set of attacks documented by the Russian cybersecurity vendor was found to target Kyrgyz organizations in late September 2025 with phishing emails containing a Microsoft Office document, which, when opened, instructs recipients to "Enable Content" so as to run a malicious macro.

While the document displays a telecom provider's tariff plan to the victim, the macro stealthily drops a C++ malware loader called LuciLoad that, in turn, delivers LuciDoor. Another attack observed in late November 2025 adopted the same modus operandi, only this time it used a different loader codenamed MarsSnakeLoader to deploy MarsSnake.

As recently as January 2026, UnsolicitedBooker is said to have leveraged phishing emails as a vector to target companies in Tajikistan. While the overall attack chain remains the same, the messages embedded links to the decoy documents as opposed to directly attaching them.

Written in C++, LuciDoor establishes communication with a command-and-control (C2) server, collects basic system information, and exfiltrates the data to the server in encrypted format. It then parses the responses sent by the server to run commands using cmd.exe, write files to the system, and upload files.

MarsSnake, similarly, allows attackers to harvest system metadata, execute arbitrary commands, and read or write any file on disk.

Positive Technologies said it also found signs that MarsSnake was put to use in attacks targeting China. The starting point is a Windows shortcut that masquerades as a Microsoft Word document (*.doc.lnk) that triggers the execution of a batch script to launch a Visual Basic Script, which then launches MarsSnake without the loader component.

The decoy file is believed to be based on an LNK file associated with a publicly available pentesting tool called FTPlnk_phishing, owing to the identical LNK file creation time and Machine ID indicators. It's worth noting that a similar LNK file was put to use by the Mustang Panda group in attacks targeting Thailand in 2022.

"In their attacks, the group used rare tools of Chinese origin," Positive Technologies said. "Interestingly, at the very beginning, the group used a backdoor we dubbed LuciDoor, but later switched to the MarsSnake backdoor. However, in 2026, the group made a U-turn and resumed using LuciDoor."

"Furthermore, in at least one case, we observed the attackers using a hacked router as a C2 server, and their infrastructure mimicked that of Russia in some attacks."

PseudoSticky and Cloud Atlas Target Russia

The disclosure comes as a previously unknown threat actor is deliberately mimicking the tactics of a pro-Ukrainian hacking group called Sticky Werewolf (aka Angry Likho, MimiStick, and PhaseShifters) to attack Russian organizations in the retail, construction, and research sectors with malware like RemcosRAT and DarkTrack RAT for comprehensive data theft and remote control.

The new group, referred to as PseudoSticky, has been active since November 2025. Victims are typically infected by phishing emails containing malicious attachments that lead to the deployment of the trojans. There are indications that the threat actor has relied on large language models (LLMs) to develop attack chains that drop DarkTrack RAT via PureCrypter.

"A closer analysis reveals differences in the infrastructure, malware implementation, and individual tactical elements, leading us to suspect that there is likely no direct connection between the groups, but rather deliberate mimicry," Russian security vendor F6 said.

Russian entities have also been targeted by another hacking group called Cloud Atlas, using phishing emails bearing malicious Word documents to distribute custom malware known as VBShower and VBCloud.

"When opened, the malicious document loads a remote template from C2 specified in one of the document's streams," cybersecurity company Solar said. "This template exploits the CVE-2018-0802 vulnerability. This is followed by downloading a malicious file with alternate streams, i.e., VBShower."



from The Hacker News https://ift.tt/yqsrfZ2
via IFTTT

Monday, February 23, 2026

Run OpenClaw Securely in Docker Sandboxes

Docker Sandboxes is a new primitive in the Docker’s ecosystem that allows you to run AI agents or any other workloads in isolated micro VMs. It provides strong isolation, convenient developer experience and a strong security boundary with a network proxy configurable to deny agents connecting to arbitrary internet hosts. The network proxy will also conveniently inject the API keys, like your ANTHROPIC_API_KEY, or OPENAI_API_KEY in the network proxy so the agent doesn’t have access to them at all and cannot leak them. 

In a previous article I showed how Docker Sandboxes lets you install any tools an AI agent might need, like a JDK for Java projects or some custom CLIs, into a container that’s isolated from the host. Today we’re going a step further: we’ll run OpenClaw, an open-source AI coding agent, on a local model via Docker Model Runner.

No API keys, no cloud costs, fully private. And you can do it in 2-ish commands.

Quick Start

Make sure you have Docker Desktop and that Docker Model Runner is enabled (Settings → Docker Model Runner → Enable), then pull a model:

docker model pull ai/gpt-oss:20B-UD-Q4_K_XL

Now create and run the sandbox:

docker sandbox create --name openclaw -t olegselajev241/openclaw-dmr:latest shell .
docker sandbox network proxy openclaw --allow-host localhost
docker sandbox run openclaw

Inside the sandbox:

~/start-openclaw.sh
Running OpenClaw inside a Docker Sandbox

And that’s it. You’re in OpenClaw’s terminal UI, talking to a local gpt-oss model on your machine. The model runs in Docker Model Runner on your host, and OpenClaw runs completely isolated in the sandbox: it can only read and write files in the workspace you give it, and there’s a network proxy to deny connections to unwanted hosts. 

Cloud models work too

The sandbox proxy will automatically inject API keys from your host environment. If you have ANTHROPIC_API_KEY or OPENAI_API_KEY set, OpenClaw can run cloud models,  just specify them in OpenClaw settings. The proxy takes care of credential injection, so your keys will never be exposed inside the sandbox.

This means you can use free local models for experimentation, then switch to cloud models for serious work all in the same sandbox. With cloud models you don’t even need to allow to proxy to host’s localhost, so don’t run docker sandbox network proxy openclaw --allow-host localhost.

Choose Your Model

The startup script automatically discovers models available in your Docker Model Runner. List them:

~/start-openclaw.sh list

Use a specific model:

~/start-openclaw.sh ai/qwen2.5:7B-Q4_K_M

Any model you’ve pulled with docker model pull is available.

How it works (a bit technical)

The pre-built image (olegselajev241/openclaw-dmr:latest) is based on the shell sandbox template with three additions: Node.js 22, OpenClaw, and a tiny networking bridge.

The bridge is needed because Docker Model Runner runs on your host and binds to localhost:12434. But localhost inside the sandbox means the sandbox itself, not your host. The sandbox does have an HTTP proxy, at host.docker.internal:3128, that can reach host services, and we allow it to reach localhost with docker sandbox network proxy --allow-host localhost.

The problem is OpenClaw is Node.js, and Node.js doesn’t respect HTTP_PROXY environment variables. So we wrote a ~20-line bridge script that OpenClaw connects to at 127.0.0.1:54321, which explicitly forwards requests through the proxy to reach Docker Model Runner on the host:

OpenClaw → bridge (localhost:54321) → proxy (host.docker.internal:3128) → Model Runner (host localhost:12434)

The start-openclaw.sh script starts the bridge, starts OpenClaw’s gateway (with proxy vars cleared so it hits the bridge directly), and runs the TUI.

Build Your Own

Want to customize the image or just see how it works? Here’s the full build process. 

1. Create a base sandbox and install OpenClaw

docker sandbox create --name my-openclaw shell .
docker sandbox network proxy my-openclaw --allow-host localhost
docker sandbox run my-openclaw

Now let’s install OpenClaw in the sandbox:

# Install Node 22 (OpenClaw requires it)
npm install -g n && n 22
hash -r

# Install OpenClaw
npm install -g openclaw@latest

# Run initial setup
openclaw setup

2. Create the Model Runner bridge

This is the magic piece — a tiny Node.js server that forwards requests through the sandbox proxy to Docker Model Runner on your host:

cat > ~/model-runner-bridge.js << 'EOF'
const http = require("http");
const { URL } = require("url");

const PROXY = new URL(process.env.HTTP_PROXY || "http://host.docker.internal:3128");
const TARGET = "localhost:12434";

http.createServer((req, res) => {
  const proxyReq = http.request({
    hostname: PROXY.hostname,
    port: PROXY.port,
    path: "http://" + TARGET + req.url,
    method: req.method,
    headers: { ...req.headers, host: TARGET }
  }, proxyRes => {
    res.writeHead(proxyRes.statusCode, proxyRes.headers);
    proxyRes.pipe(res);
  });
  proxyReq.on("error", e => { res.writeHead(502); res.end(e.message); });
  req.pipe(proxyReq);
}).listen(54321, "127.0.0.1");
EOF

3. Configure OpenClaw to use Docker Model Runner

Now merge the Docker Model Runner provider into OpenClaw’s config:

python3 -c "
import json
p = '$HOME/.openclaw/openclaw.json'
with open(p) as f: cfg = json.load(f)
cfg['models'] = cfg.get('models', {})
cfg['models']['mode'] = 'merge'
cfg['models']['providers'] = cfg['models'].get('providers', {})
cfg['models']['providers']['docker-model-runner'] = {
    'baseUrl': 'http://127.0.0.1:54321/engines/llama.cpp/v1',
    'apiKey': 'not-needed',
    'api': 'openai-completions',
    'models': [{
        'id': 'ai/qwen2.5:7B-Q4_K_M',
        'name': 'Qwen 2.5 7B (Docker Model Runner)',
        'reasoning': False, 'input': ['text'],
        'cost': {'input': 0, 'output': 0, 'cacheRead': 0, 'cacheWrite': 0},
        'contextWindow': 32768, 'maxTokens': 8192
    }]
}
cfg['agents'] = cfg.get('agents', {})
cfg['agents']['defaults'] = cfg['agents'].get('defaults', {})
cfg['agents']['defaults']['model'] = {'primary': 'docker-model-runner/ai/qwen2.5:7B-Q4_K_M'}
cfg['gateway'] = {'mode': 'local'}
with open(p, 'w') as f: json.dump(cfg, f, indent=2)
"

4. Save and share

Exit the sandbox and save it as a reusable image:

docker sandbox save my-openclaw my-openclaw-image:latest

Push it to a registry so anyone can use it:

docker tag my-openclaw-image:latest yourname/my-openclaw:latest
docker push yourname/my-openclaw:latest

Anyone with Docker Desktop (with the modern sandboxes includes) can spin up the same environment with:

docker sandbox create --name openclaw -t yourname/my-openclaw:latest shell .

What’s next

Docker Sandboxes make it easy to run any AI coding agent in an isolated, reproducible environment. With Docker Model Runner, you get a fully local AI coding setup: no cloud dependencies, no API costs, and complete privacy.

Try it out and let us know what you think.



from Docker https://ift.tt/iatRnHw
via IFTTT

⚡ Weekly Recap: Double-Tap Skimmers, PromptSpy AI, 30Tbps DDoS, Docker Malware & More

Security news rarely moves in a straight line. This week, it feels more like a series of sharp turns, some happening quietly in the background, others playing out in public view. The details are different, but the pressure points are familiar.

Across devices, cloud services, research labs, and even everyday apps, the line between normal behavior and hidden risk keeps getting thinner. Tools meant to protect, update, or improve systems are also becoming pathways when something goes wrong.

This recap gathers the signals in one place. Quick reads, real impact, and developments that deserve a closer look before they become next week’s bigger problem.

⚡ Threat of the Week

Dell RecoverPoint for VMs Zero-Day Exploited — A maximum severity security vulnerability in Dell RecoverPoint for Virtual Machines has been exploited as a zero-day by a suspected China-nexus threat cluster dubbed UNC6201 since mid-2024. The activity involves the exploitation of CVE-2026-22769 (CVSS score: 10.0), a case of hard-coded credentials affecting versions prior to 6.0.3.1 HF1. Per Google, the hard-coded credential relates to an "admin" user for the Apache Tomcat Manager instance that could be used authenticate to the Dell RecoverPoint Tomcat Manager, upload a web shell named SLAYSTYLE via the "/manager/text/deploy" endpoint, and execute commands as root on the appliance to drop the BRICKSTORM backdoor and its newer version dubbed GRIMBOLT.

🔔 Top News

  • Former Google Engineers Indicted Over Alleged Trade Secret Theft — Two former Google engineers and one of their husbands have been indicted in the U.S. for allegedly committing trade secret theft from the search giant and other tech firms and transferring the information to unauthorized locations, including Iran. Samaneh Ghandali, 41, and her husband Mohammadjavad Khosravi (aka Mohammad Khosravi), 40, along with her sister Soroor Ghandali, 32, were accused of conspiring to commit trade secret theft from Google and other leading technology companies, theft and attempted theft of trade secrets, and obstruction of justice. The defendants are said to have transferred hundreds of sensitive files to a third-party communications platform and then accessed them from Iran after Samaneh Ghandali and Khosravi traveled to Iran in December 2023.
  • PromptSpy Android Malware Abuses Gemini for Persistence — Researchers at ESET analyzed what they described as the first Android malware to leverage generative artificial intelligence (AI) during its execution to set up persistence. Called PromptSpy, the malware uses Google Gemini to analyze the current screen and provide step-by-step instructions on how to ensure the malicious app remains pinned in the recent apps list by taking advantage of the operating system's accessibility services. There are signs that the campaign is likely targeting users in Argentina. Google told The Hacker News that it did not find any apps containing the malware being distributed via Google Play.
  • Kenyan Dissident's Phone Cracked Using Cellebrite's Tool — Evidence has emerged that Kenyan authorities used a commercial forensic extraction tool manufactured by Israeli company Cellebrite to break into a prominent dissident's phone. The Citizen Lab said it found the indicators on a personal phone belonging to Boniface Mwangi, a Kenyan pro-democracy activist who has announced plans to run for president in 2027. In a related development, Amnesty International found that the iPhone belonging to Teixeira Cândido, an Angolan journalist and press freedom advocate, was successfully targeted by Intellexa's Predator spyware in May 2024 after he opened an infected link received via WhatsApp.
  • New Pre-Installed Android Malware Keenadu Detected in the Wild — A new Android backdoor that's embedded deep into the device firmware can silently harvest data and remotely control its behavior, Kaspersky said. The malware, codenamed Keenadu, is said to have been delivered by means of compromised firmware through an over-the-air (OTA) update. This method allows it to run with high privileges from the moment the device is activated, providing attackers with extensive control over the device. It can also infect other installed apps, deploy additional software from APK files, and grant those apps any permission available on the system. Once active, Keenadu inherits elevated permissions and operates with minimal visibility. The malware triggers only under specific conditions, remaining dormant on devices set to Chinese languages or time zones and on those that lack the Google Play Store and Google Play Services. However, Keenadu's distribution is not limited to pre-installed system components. In some cases, the malware has also been observed embedded within applications distributed through Android app stores. That said, there is very little a user can do when a piece of malware comes pre-installed on their brand new Android tablet. Because the malicious components are present in firmware rather than installed later as apps, affected users may have limited ability to detect or remove them through conventional methods. The activity has not been attributed to a specific threat actor, but Kaspersky said the developers demonstrated "a deep understanding of the Android architecture, the app startup process, and the core security principles of the operating system."
  • Password Managers' Zero Knowledge Claims Put to Test — A new study undertaken by researchers from ETH Zurich and Università della Svizzera italiana has undermined claims from Bitwarden, Dashlane, and LastPass that the password managers guarantee "zero knowledge" -- an assurance that states there is no way for a malicious insider or a threat actor that has compromised the cloud infrastructure to access the vault data. Specifically, it found that these claims are not true under all circumstances, particularly when account recovery is in place, or password managers are set to share vaults or organize users into groups. The most severe of the attacks, targeting Bitwarden and LastPass, could allow an insider or attacker to read or write to the contents of entire vaults. Other attacks enable reading and modification of shared vaults. "Attacks on the provider server infrastructure can be prevented by carefully designed operational security measures, but it is well within the bounds of reason to assume that these services are targeted by sophisticated nation-state-level adversaries, for example via software supply-chain attacks or spear-phishing," the researchers said.

‎️‍🔥 Trending CVEs

New vulnerabilities surface daily, and attackers move fast. Reviewing and patching early keeps your systems resilient.

Here are this week’s most critical flaws to check first — CVE-2026-22769 (Dell RecoverPoint for Virtual Machines), CVE-2026-25926 (Notedpad++), CVE-2026-26119 (Microsoft Windows Admin Center), CVE-2026-2329 (Grandstream GXP1600 series), CVE-2025-65717 (Live Server), CVE-2026-1358 (Airleader Master), CVE-2026-25108 (FileZen), CVE-2026-25084, CVE-2026-24789 (ZLAN), CVE-2026-2577 (Nanobot), CVE-2026-25903 (Apache NiFi), CVE-2026-26019 (@langchain/community), CVE-2026-1670 (Honeywell CCTV), CVE-2025-7740 (Hitachi Energy SuprOS), CVE-2025-61928 (better-auth), CVE-2026-20140 (Splunk Enterprise for Windows), CVE-2026-27118 (@sveltejs/adapter-vercel), CVE-2026-27099, CVE-2026-27100 (Jenkins), CVE-2026-24733 (Apache Tomcat), CVE-2026-2648, CVE-2026-2649, CVE-2026-2650 (Google Chrome), CVE-2025-29969 (Windows Fundamentals), CVE-2025-64127, CVE-2025-64128, CVE-2025-64129, CVE-2025-64130 (Zenitel), CVE-2025-32355, CVE-2025-59793 (TRUfusion Enterprise), CVE-2026-1357 (WPvivid Backup plugin), CVE-2025-9501 (W3 Total Cache plugin), CVE-2025-13818 (ESET Management Agent for Windows), CVE-2025-11730 (ZYXEL ATP/USG series), CVE-2025-67303 (ComfyUI), and Joomla! unauthenticated file read, unauthenticated file deletion, and SQL injection vulnerabilities in Novarain/Tassos Framework (no CVEs).

🎥 Cybersecurity Webinars

  • Learn How to Future-Proof Your Encryption Before Quantum Breaks It → Quantum computing is accelerating, and attackers are harvesting encrypted data for future decryption. This webinar covers practical post-quantum cryptography, hybrid encryption, and Zero Trust strategies to protect sensitive data before quantum threats become real.
  • Beyond the Model: Securing AI Agents in Real-World Systems → As organizations deploy autonomous AI agents with tool access and system permissions, the attack surface shifts beyond the model itself. This session explores indirect prompt injection, privilege escalation, multi-agent risk, and practical strategies to secure real-world AI systems without breaking workflows.
  • Pressure-Test Your Controls With Continuous CTI-Driven Validation → Security budgets are rising, yet breaches continue. This session shows how to move beyond assumption-based testing to continuous, CTI-driven exposure validation—pressure-testing controls against real attacker behavior, automating security checks, and building measurable resilience without overspending.

📰 Around the Cyber World

  • Online Store Infected with Skimmer — The online store of a top-10 global supermarket chain has been infected with a skimmer malware that scans for admin users for WordPress, Magento, PrestaShop, and OpenCart to evade detection. "The attack combines two components: a seemingly off-the-shelf skimmer framework with integrations for four popular e-commerce platforms, and a carefully localized fake payment form," Sansec said. "This fraud is called 'double-tap skimming': customers enter their card details into the fake form first, then see the real payment form where they have to enter their data again. Most people just accept that and complete the order, unaware their data was just stolen." The breach coincides with a broader wave of attacks targeting PrestaShop stores. In January 2026, PrestaShop urged merchants to check their stores for skimmers injected into theme template files.
  • Nigeria Arrests 7 for Running Scam Center — Nigerian authorities arrested seven suspects who ran a cyber scam center in the city of Agbor. The group used social media ads to lure U.K. victims to bogus crypto investment portals. Hundreds of fake Facebook accounts were potentially used to target victims. "Using these bogus social media accounts to impersonate cryptocurrency traders, they targeted people who used legitimate investment platforms, sharing false positive reviews to lure people into sending money to the fraudsters," the U.K. National Crime Agency (NCA) said. Meta said it's working with law enforcement to identify and remove all accounts used in these operations. "The group used fake social media accounts impersonating cryptocurrency traders, along with fraudulent Facebook groups featuring fabricated testimonials, to target individuals engaging with legitimate investment platforms," it added. In the first half of 2025, the company noted it took down 12 million accounts across Facebook, Instagram, and WhatsApp associated with criminal scam centers.
  • LonTalk Protocol Analyzed — Claroty has called attention to security risks posed by the LonTalk proprietary protocol that's used for device-to-device communication in building management and automation systems (BMS and BAS). "LonTalk should not be underestimated as an attack vector for hacktivists and criminal entities, especially as BMS is enabled over IP networks," the company said. "LonTalk is certainly still relevant to BMS cybersecurity discussions, especially as BMS finds its way online for a number of strategic and bottom-line reasons. Commercial real estate, retail, hospitality, and data center sectors rely on BMS systems such as HVAC (heating, ventilation, and air conditioning), lighting, energy management, and security. Previously, these systems were operated independently by facility management, but they are now increasingly connected and integrated through advanced BMS and BAS capabilities."
  • GrayCharlie Uses Compromised WordPress Sites to Deliver RATs — A threat actor known as GrayCharlie (aka HANEYMANEY, SmartApeSG, and ZPHP) has been observed compromising WordPress sites and injecting them with links to externally hosted JavaScript that redirects visitors to NetSupport RAT payloads delivered via fake browser update pages or ClickFix mechanisms. The threat first emerged in mid-2023. "These infections often progress to the deployment of StealC and SectopRAT," Recorded Future said. While most compromised websites appear to be opportunistic and span numerous industries, the cybersecurity company said it identified a cluster of U.S. law firm sites that were likely compromised around November 2025, likely through a supply chain attack involving a shared IT provider.
  • Why Patch Everything is a Recipe for Burnout — Dataminr's 2026 Cyber Threat Landscape Report has revealed that the "patching treadmill is broken," driven by reliance on CVSS scores and a surge in patch bypasses, where vendors don't address the root causes of issues, thereby opening the door to re-exploitation by threat actors days or weeks after the initial patch was released. "With thousands of CVEs disclosed every year, security teams can’t just rely on the common vulnerability severity score (CVSS) to decide what to patch," Dataminr said. "These scores focus on the technical impacts of a vulnerability, but tell you very little about actual risk to your organization. There has to be a balance between the CVSS, potential economic impact, exposure, and likelihood of being targeted. The focus has to shift from 'is this a critical CVE?' to 'is this specific flaw being targeted in my sector, and can the attacker actually reach my crown jewels through it?'"
  • Phishing Campaigns in Taiwan Deliver Winos 4.0 — Targeting phishing campaigns have targeted Taiwan with themes designed to exploit local business processes and ultimately deliver a known remote access trojan called Winos 4.0 (aka ValleyRAT) and malicious plugins through weaponized attachments or embedded links. "The lures mimic official communications, such as tax audit notifications, tax filing software installers, and cloud-based e-invoice downloads," Fortinet FortiGuard Labs said. "Over the past two months, we have identified various delivery techniques, including malicious LNK files used for a downloader, DLL side-loading via legitimate executables to load shellcode, and BYOVD (Bring Your Own Vulnerable Driver) attacks using 'wsftprm.sys.'" The driver is used to terminate processes associated with a hard-coded list of security products. The use of Winos 4.0 is unique to a Chinese cybercrime group known as Silver Fox.
  • Teams Gets Brand Impersonation Protection — Microsoft said it will start rolling out Brand Impersonation Protection for Teams Calling starting mid-March 2026 to detect and warn users of suspicious external calls to reduce fraud risks. "It will be enabled by default, requires no admin action, and aims to enhance security without changing existing policies," Microsoft said. The tech giant is also planning to introduce a "Report a Call" feature by mid-March 2026 to let users flag suspicious one-to-one calls.
  • 2025 Records 508 ICS advisories from CISA — Between March 2010 and January 31, 2026, CISA/ICS-CERT published 3,637 ICS advisories about 12,174 vulnerabilities affecting 2,783 products from 689 vendors, Forescout said. 2025 recorded a high of 508 ICS advisories, covering 2,155 vulnerabilities across various products and vendors. The development marks the first year exceeding 500 advisories. The average severity rose to a CVSS score of 8.07 and 82% of advisories were classified as high or critical. In contrast, back in 2010, the average was 6.44, and it was classified as medium severity.
  • Microsoft Unveils LiteBox — Microsoft has released LiteBox, a Rust-based project described as a "sandboxing library OS that drastically cuts down the interface to the host, thereby reducing attack surface." Developed in collaboration with the Linux Virtualization Based Security (LVBS) project, the goal is to sandbox applications by minimizing host system interactions and supporting various use cases like running Linux programs on Windows or sandboxing Linux applications.
  • ChainedShark Targets Chinese Research Sector — A new APT group codenamed ChainedShark is targeting China's academic and scientific research sector. Active since May 2024, the group's main focus has been the collection of intelligence on Chinese diplomacy and marine technology. Past victims include universities and research institutions specializing in international relations. Its arsenal integrates N-day vulnerability exploits and highly complex custom trojans such as LinkedShell. "ChainedShark exhibits clear geopolitical motivations, focusing its attacks on experts and scholars in international relations and marine sciences within Chinese academic and research institutions," NSFOCUS said. "The group demonstrates strong social engineering capabilities, crafting fluent, natural, and high-quality Chinese-language lures. It skillfully exploits professional scenarios—such as conference invitations and academic call-for-papers—to create deceptive attack vectors, effectively lowering targets' guard."
  • Samsung Weather App as a Way for User Fingerprinting — New research has uncovered that Samsung's pre-installed weather app is fingerprinting its users by means of a "placeid" parameter that's trivially observable by the weather API provider. A test conducted on 42 Samsung devices found that the fingerprints were unique per device and survived IP changes across providers and VPN use. "Analysis of 9,211 weather API requests from 42 Samsung device owners over five days demonstrates that placeid combinations produce unique user identifiers in 96.4% of cases," Buchodi's Threat Intel said. "Every user with two or more saved locations had a fingerprint shared by no one else in the dataset." This, in turn, turns saved locations into a persistent cross-session tracking identifier, as each placeid identifies a unique location. The fingerprint represents an aggregate of all placeid values associated with a device's saved locations. In other words, a user tracking a combination of more than two or three locations can be uniquely identified.
  • DDoS Attacks Jump 168% in 2025 — A new analysis released by Radware has revealed that the number of web DDoS attacks climbed 101.4% in 2025 compared to 2024, and bad bot activity increased 91.8%, fueled by generative AI tools. Malicious web application and API transactions rose 128% year over year. Network-layer DDoS attacks increased 168.2% year over year, with peak attack volumes reaching almost 30 terabits per second (Tbps). "Technology, telecommunications, and financial services were the most targeted sectors, together accounting for the majority of large-scale network DDoS campaigns," Radware said. "The technology sector alone represented 45% of all network-layer DDoS attacks, up sharply from 8.77% in 2024." Hacktivism, fueled by geopolitical and ideological conflict, remained a primary driver of DDoS activity.
  • Over 2,500 Malicious Images Flagged on Docker Hub — Qualys said it discovered more than 2,500 malicious images hosted on the Docker Hub. Of these, around 70% of them contained a hidden cryptominer. Others included backdoors, exploits, ransomware, keyloggers, and proxy infrastructure. "Pulling container images from public registries is no longer a neutral operational step," the company said. "It is a trust decision that directly affects infrastructure stability, cloud costs, and security risk."
  • Nearly 1T Scam Ads Served on Social Media in 2025 — According to new findings from Juniper Research, online tech platforms made £3.8 billion ($5.2 billion) in revenue from malicious or scam ads in Europe alone. Nearly 1 trillion scam ads were served to social media users in 2025. The analyst firm also revealed earlier this month that e-commerce fraud will rise from $56bn in 2025 to $131 billion in 2030, posting a 133% increase over the period.
  • Malicious npm Packages Hijack Gambling Outcomes — Researchers have discovered malicious npm packages, json-bigint-extend, jsonfx, and jsonfb, that mimic the legitimate json-bigint library, but contain functionality to install two backdoors to execute additional code fetched from an endpoint, run arbitrary SQL commands, download file contents, and list server-side files and directories. "Upon further inspection of the fetched code, it seems to be a complex cashflow-rewriting system used to manipulate a gambling game," Aikido said. "The most sophisticated component of this backdoor is the fixFlow function, a balance manipulation engine that retroactively rewrites a user's gambling history to achieve a desired balance change while maintaining the appearance of legitimate gameplay." It's suspected that the malware is designed to target a gambling app named Bappa Rummy. It's no longer listed on the official Google Play Store.
  • Telegram Disputes Claims About Encryption — The head of Russia's FSB security service accused Telegram of harboring criminal activity and failing to act on reports from Russian authorities. Bortnikov said Telegram ignored more than 150,000 requests for removal from Russian authorities. Russian officials also claimed that foreign intelligence services could read messages sent by Russian soldiers over the app. The messaging platform said "no breaches of Telegram's encryption have ever been found." The development comes as Russia started blocking and throttling Telegram traffic last week.
  • Nigerian Man Sentenced to Eight Years in Prison for Bogus Tax Refund Scheme — A 37-year-old Nigerian man named Matthew A. Akande, who was living in Mexico, was sentenced to eight years in prison in the U.S. for his involvement in a criminal operation that involved unauthorized access to the computer networks of tax preparation firms in Massachusetts. Between in or about June 2016 and June 2021, Akande conspired to use stolen taxpayer information to file over 1,000 fraudulent tax returns seeking millions of dollars in tax refunds, the Justice Department said. The defendant was also ordered to pay $1,393,230 in restitution. He was arrested in October 2024 in the U.K. and extradited to the U.S. in March 2025. "To carry out the scheme, Akande caused fraudulent phishing emails to be sent to five Massachusetts tax preparation firms," the department said. The emails purported to be from a prospective client seeking the tax preparation firms’ services, but in truth were used to trick the firms into downloading remote access trojan malicious software (RAT malware), including malware known as Warzone RAT. Akande used the RAT malware to obtain the PII and prior year tax information of the tax preparation firms' clients, which Akande then used to cause fraudulent tax returns to be filed seeking refunds." Warzone RAT's infrastructure was seized by the U.S. Federal Bureau of Investigation in February 2024.
  • New Campaigns Distribute njRAT, Pulsar RAT, XWorm, and Prometei — In a new campaign, threat actors are leveraging the njRAT remote access trojan to deliver the MassLogger infostealer. Another campaign has been found to use a Donut loader to distribute Pulsar RAT as part of a sophisticated, multi-stage malware attack. What's notable about this activity is that Pulsar RAT is used to actively control a compromised host, allowing an attacker to initiate a real-time chat session with the victim to interact and probe system usage. Also discovered are two campaigns using phishing emails to distribute XWorm: One uses a JavaScript dropper to target Brazilian users, and another begins with phishing emails delivering a malicious Excel attachment to targeted users. The Excel file exploits CVE-2018-0802, a memory corruption flaw in Office patched in 2018, to download and execute an HTA file on the victim's device, which, in turn, triggers PowerShell to download and run a fileless .NET module directly into memory. The module then uses process hollowing to inject and execute the XWorm payload within a newly created MSBuild.exe process. Last but not least, Windows servers are being targeted by threat actors to infect them with a botnet known as Prometei. "It features extensive capabilities, including remote control functionality, credential harvesting, crypto-mining (Monero), lateral movement, command-and-control (C2) over both the clearweb and TOR network, and self-preservation measures that harden compromised systems against other threat actors, to maintain exclusive access," eSentire said.
  • Gixy Next → It is an open-source security analysis tool designed to audit NGINX configurations for common misconfigurations and vulnerabilities. It scans configuration files to detect issues such as unsafe directives, incorrect access controls, and insecure proxy settings that could expose applications to attacks. Built as a successor to the original Gixy project, it aims to provide updated checks and improved rule coverage for modern NGINX deployments.
  • The-One-WSL-BOF → It is an open-source Cobalt Strike Beacon Object File that lets operators interact with Windows Subsystem for Linux (WSL) directly from a Beacon session. It can list WSL distributions and run commands inside them without launching wsl.exe, reducing visible process activity and some logging artifacts.

Disclaimer: These tools are provided for research and educational use only. They are not security-audited and may cause harm if misused. Review the code, test in controlled environments, and comply with all applicable laws and policies.

Conclusion

If one theme runs through this week, it is quiet exposure. Risk is showing up in routine updates, trusted tools, and features most teams rarely question until something breaks.

The real issue is not a single flaw but the pattern beneath it. Small weaknesses are being chained together and scaled with automation faster than defenders can adjust.

Scan the full list carefully. One of these short updates will likely map closer to your own environment than it first appears.



from The Hacker News https://ift.tt/vJjSP1f
via IFTTT