The campaign highlights a growing trend in which threat actors are shifting their focus from traditional Linux servers to AI platforms that power Large Language Model (LLM) applications and Retrieval-Augmented Generation (RAG) workflows.

The vulnerability affects Langflow versions up to 1.8.2, has received a CVSS score of 9.8, and has been added to CISA’s Known Exploited Vulnerabilities (KEV) catalog due to active exploitation. The issue has been addressed in Langflow version 1.9.0.

How the Attack Works

The vulnerability exists in Langflow’s public workflow execution endpoint, where insufficient input validation allows attackers to inject and execute malicious Python code without authentication. Researchers also noted that AUTO_LOGIN is enabled by default, allowing unauthenticated users to obtain a superuser token and create public workflows, making exploitation significantly easier on exposed servers.

The attack begins with automated reconnaissance. Threat actors rapidly scan internet-facing Langflow instances using multiple browser user-agent strings while probing endpoints such as /health, /api/v1/version, and /manifest.json. This approach helps identify vulnerable systems while reducing the likelihood of detection.

Once a vulnerable server is identified, attackers exploit the flaw by sending a specially crafted request that downloads and executes a malicious shell script. Researchers observed the same workflow identifier being reused across multiple attacks, suggesting the campaign is highly automated.

The shell script acts as a dropper, creating hidden directories, downloading the primary malware, and launching it in the background. It also searches for SSH keys, known hosts, and active SSH agent sessions in an attempt to spread laterally to additional Linux systems.

Cryptominer Deployment and Persistence

The primary payload is a UPX-packed Go binary designed to establish persistence while preparing the system for cryptocurrency mining.

Researchers observed the malware performing several actions after execution:

• Downloading a customized XMRig-based Monero miner.
• Terminating dozens of competing cryptomining processes already running on the system.
• Removing backdoor accounts left behind by previous malware campaigns.
• Increasing system resource limits to improve mining performance.

To avoid detection, the malware disables several Linux security controls, including AppArmor, SELinux, UFW, iptables, the Linux NMI watchdog, and Alibaba Cloud’s Aliyun security agent. It also clears system logs, removes file protection attributes, and modifies system settings to make forensic analysis more difficult.

For long-term persistence, the malware creates scheduled cron jobs and watchdog processes that automatically restore the miner if it is removed. It also locks critical files and directories, making cleanup significantly more challenging.

The customized Monero miner is installed inside a hidden directory and connects to attacker-controlled mining infrastructure over TCP port 3333. Researchers also observed regular heartbeat communications with command-and-control servers, allowing attackers to monitor infected systems and maintain control of the campaign.

Why AI Servers Are Being Targeted

Langflow is commonly integrated with cloud platforms, AI models, databases, and external APIs. As a result, compromised servers often contain valuable API keys, cloud credentials, database passwords, and SSH keys.

During the attacks, researchers observed threat actors searching for environment files and sensitive credentials that could enable lateral movement or provide access to additional enterprise resources. This makes the impact far greater than unauthorized cryptocurrency mining alone.

Security Recommendations

Organizations using Langflow should immediately upgrade to version 1.9.0 or later and ensure that vulnerable instances are not directly accessible from the internet.

Security teams should also:

• Restrict public access to Langflow deployments.
• Monitor for unusual API requests and unexpected Python execution.
• Review systems for unauthorized cron jobs, background processes, and persistence mechanisms.
• Rotate exposed API keys, SSH credentials, and cloud secrets if compromise is suspected.
• Investigate unusual outbound connections and signs of cryptocurrency mining activity.

The rapid exploitation of CVE-2026-33017 demonstrates how quickly attackers weaponize vulnerabilities in AI platforms. As organizations continue adopting AI technologies, securing AI infrastructure should become a core part of enterprise cybersecurity strategies, alongside continuous monitoring, timely patch management, and strong access controls.

IoCs

File Hashes (SHA-256)

Network Indicators

The post Langflow Vulnerability Deploys Monero Miner appeared first on First Hackers News.

The notification covers multiple products, including NGINX Open Source, NGINX Plus, NGINX Instance Manager, NGINX Gateway Fabric, NGINX Ingress Controller, and App Protect security modules. According to F5, organizations using affected versions should prioritize updates to reduce exposure to active threats.

Critical Vulnerabilities Impact HTTP/3, HTTP/2, and gRPC Services

Among the most serious issues is CVE-2026-42530, a vulnerability within the NGINX HTTP/3 module. Attackers can exploit specially crafted HTTP/3 requests to trigger memory-related errors, causing worker processes to crash repeatedly. In certain environments, the flaw may also open a path for remote code execution.

Another high-risk vulnerability, CVE-2026-42055, affects deployments that utilize HTTP/2 or gRPC proxying. Malicious traffic can abuse weaknesses in request handling, potentially leading to service interruptions, application crashes, and in some cases, code execution risks.

Key concerns include:

• Potential remote code execution on vulnerable systems
• Denial-of-service conditions causing service outages
• Increased risk for environments using HTTP/3, HTTP/2, and gRPC
• Exposure across several NGINX-based products and services

Gateway Fabric Vulnerabilities Add Additional Risk

F5 also highlighted multiple high-severity vulnerabilities impacting NGINX Gateway Fabric deployments. These issues can affect traffic routing reliability, application availability, and overall service stability in cloud-native and gateway environments.

To address the risks, F5 has released updated versions containing security fixes and recommends that customers:

• Upgrade affected NGINX products immediately
• Review exposed HTTP/2, HTTP/3, and gRPC services
• Verify that security patches have been applied successfully
• Update Gateway Fabric deployments to the latest supported release

The advisory serves as a reminder that organizations relying on modern web application infrastructure should maintain a proactive patch management strategy, particularly when vulnerabilities affect core traffic-processing components.

Recommended Security Actions

F5 urges customers to update affected NGINX products to the latest secure versions as soon as possible.

For systems that cannot be patched immediately, organizations should disable unnecessary HTTP/3 and QUIC services, limit HTTP/2 and gRPC exposure, strengthen access controls, and enable security hardening measures to reduce the risk of exploitation.

The post F5 NGINX Vulnerabilities Patched in Critical Security Update appeared first on First Hackers News.

What makes Rokarolla particularly dangerous is its scale. Researchers observed the malware targeting 217 banking and cryptocurrency applications while providing operators with 137 remote commands, significantly expanding its capabilities beyond many previously documented Android banking trojans.

Threat Overview

Malware Name

Rokarolla

Malware Type

• Android Banking Trojan
• Malware-as-a-Service (MaaS)
• Credential Stealer
• Remote Access Trojan (RAT)

Primary Targets

• Mobile banking users
• Cryptocurrency investors
• Android smartphone users
• Financial institutions

How Rokarolla Infects Devices

The malware is typically distributed through malicious APK files disguised as legitimate applications. Victims are tricked into installing fake apps through phishing pages, malicious advertisements, fraudulent updates, or third-party application stores.

Once installed, Rokarolla aggressively requests permissions that allow it to interact with the Android Accessibility Service. This permission becomes the foundation for most of the malware’s malicious activities.

Accessibility Service Abuse

Android Accessibility Services were designed to assist users with disabilities. However, threat actors frequently abuse these permissions because they allow applications to:

• Read screen content
• Simulate user interactions
• Click buttons automatically
• Capture text entered by users

Rokarolla leverages these capabilities to monitor activity across banking and cryptocurrency applications while bypassing many traditional security mechanisms.

Google Play Protect Bypass

One of Rokarolla’s most concerning features is its ability to disable or interfere with Google Play Protect.

Why This Is Dangerous

Google Play Protect serves as Android’s primary built-in malware detection system. Once disabled:

• Malicious applications face fewer detection checks
• Additional malware can be installed
• Security warnings can be bypassed
• Users lose a critical layer of protection

Remote Device Control Capabilities

Researchers identified 137 attacker commands supported by Rokarolla.

These commands allow threat actors to remotely interact with infected devices and perform a wide range of malicious actions.

• Read SMS messages
• Send SMS messages
• Collect contacts
• Launch applications
• Execute commands

SMS and Two-Factor Authentication Interception

Many financial institutions rely on SMS-based two-factor authentication (2FA).

Rokarolla specifically targets these messages to bypass security controls.

Targeted Data

• One-Time Passwords (OTPs)
• Verification codes
• Authentication links
• Banking notifications

Cryptocurrency Theft Mechanism

Researchers discovered clipboard manipulation functionality within Rokarolla.

How It Works

1. User copies a cryptocurrency wallet address.
2. Malware monitors clipboard activity.
3. Original wallet address is replaced.
4. Funds are transferred to an attacker-controlled wallet.

Victims often remain unaware until the transaction has been completed because the replacement occurs silently in the background.

Indicators of Compromise (IOCs)

Security Recommendations

• Enable Google Play Protect
• Avoid Sideloading Applications
• Review Accessibility Permissions
• Keep Devices Updated

Rokarolla represents a new generation of Android banking malware that combines accessibility abuse, credential theft, SMS interception, clipboard hijacking, and Google Play Protect bypass techniques to achieve near-total control over infected devices. With support for 137 remote commands and targeting hundreds of financial applications, it demonstrates the increasing sophistication of mobile threats facing both consumers and enterprises.

The post Rokarolla Android Malware Disables Google Play Protect to Gain Full Device Control appeared first on First Hackers News.

The campaign primarily focused on compromising REDCap (Research Electronic Data Capture) servers, a widely used platform for managing clinical research databases and surveys. After gaining access, the attackers deployed custom malware called INFINITERED, harvested credentials, established persistence, and later abused enterprise email compliance rules to exfiltrate sensitive communications.

Campaign Overview

The operation demonstrates a sophisticated attack chain combining exploitation of public-facing applications, credential theft, malware deployment, persistence mechanisms, and stealthy data exfiltration.

Key Objectives

• Medical research intelligence
• Artificial Intelligence research
• Defense-related information
• Military health research Public health policy data

Researchers observed the activity from September 2023 through November 2025, indicating a highly patient and well-resourced espionage operation.

High-level attack flow used by UNC6508 to compromise research institutions and steal sensitive information.

Initial Access Through REDCap Servers

Why REDCap Was Targeted

REDCap is extensively used across:

• Hospitals
• Clinical research organizations
• Universities
• Government research programs
• Military health institutions

Because REDCap stores large volumes of research and patient-related information, it provides an attractive entry point for espionage-focused threat actors.

Researchers observed the attackers probing and exploiting vulnerable or legacy REDCap deployments exposed to the internet. Once access was obtained, they began internal reconnaissance and credential discovery activities.

Web Shell Deployment and Persistence

Following successful compromise, UNC6508 deployed a web shell identified as:

help.php

The web shell served multiple purposes:

• Persistent access
• File uploads
• Command execution
• Further malware deployment

This allowed the attackers to maintain long-term access even if passwords were changed or some security controls were implemented.

INFINITERED Malware Analysis

Three months after the initial intrusion, researchers observed deployment of a custom malware family called INFINITERED. This malware was specifically engineered to operate inside REDCap environments.

Modular architecture of INFINITERED malware used by UNC6508 to maintain persistence, harvest credentials, and execute commands within compromised REDCap environments.

Component 1 – Upgrade Interceptor

The malware monitors REDCap upgrade activities.

When administrators update REDCap, the malware automatically injects itself into newer versions, ensuring persistence across software upgrades

Component 2 – Credential Harvester

This module captures usernames and passwords entered into REDCap login pages.

Stolen credentials are stored within REDCap database tables and later retrieved by attackers.

Component 3 – Command-and-Control Backdoor

The third module acts as a fully functional backdoor.

Researchers found it could:

• Execute shell commands
• Upload files
• Download files
• Run SQL queries

Communication was hidden within HTTP cookie values, helping evade traditional detection mechanisms.

Abuse of Google Workspace for Data Exfiltration

One of the most interesting aspects of the campaign was the attackers’ use of legitimate Google Workspace functionality.

After obtaining administrative access, UNC6508 created a content compliance rule named:

Patroit

The rule automatically monitored emails containing specific keywords and forwarded matching messages to attacker-controlled Gmail accounts.

Attack Chain Breakdown

• External Reconnaissance
• Initial Compromise
• Persistence
• Privilege Escalation
• Intelligence Gathering

Potential Impact on Organizations

Organizations affected by this campaign could experience:

Research Theft

Loss of valuable intellectual property and scientific research.

Strategic Intelligence Exposure

Disclosure of defense and geopolitical information.

Credential Compromise

Unauthorized access to enterprise systems.

Regulatory Risks

Exposure of regulated healthcare and research data.

Alternative Indicators of Compromise (IOCs)

Security Recommendations

Upgrade REDCap Immediately

Remove legacy versions and apply the latest security updates.

Conduct Threat Hunting

Search for:

• help.php
• INFINITERED artifacts
• Unauthorized admin activity
• Credential harvesting indicators

The UNC6508 campaign highlights how modern nation-state threat actors are increasingly targeting research ecosystems to obtain strategic intelligence. By exploiting REDCap servers, deploying INFINITERED malware, and abusing legitimate cloud email features, the attackers maintained access for more than a year while collecting sensitive medical, defense, and technology research data. Organizations operating research platforms should prioritize patching, continuous monitoring, and proactive threat hunting to defend against similar espionage campaigns.

The post PRC-Linked Threat Actors Target REDCap Servers to Spy on U.S. Medical Research Organizations appeared first on First Hackers News.

The problem occurs when developers use i18n with sensitive attributes like links or resource paths. Normally, Angular protects applications by sanitizing input, but in this case, that protection can be bypassed. If untrusted data is directly bound to these attributes, attackers can execute scripts within the application context.

Commonly affected attributes include href, src, action, background, data, and formaction. Applications running versions between 17.x and early 22.x releases are particularly at risk, especially if they rely on user-controlled data in these areas.

Impact and Mitigation

Successful exploitation allows attackers to run malicious scripts inside a user’s browser session, which can lead to serious security issues such as:

• Session hijacking through stolen cookies or tokens
• Extraction of sensitive user data
• Performing actions on behalf of users without consent

Angular has released fixes in newer versions, and upgrading to patched releases is the most effective solution. However, older versions (like 17 and 18) still require additional precautions.

‍Follow Us on:Linkedin, Instagram, Facebook to get the latest security news!

To reduce risk, teams should follow these key practices:

• Avoid binding untrusted user input directly to sensitive HTML attributes
• Do not combine i18n with attributes that handle URLs or actions
• Apply manual sanitization using Angular’s security utilities before rendering data

Overall, this vulnerability highlights how small configuration changes can weaken built-in protections, making secure coding practices and timely updates critical for Angular applications.

The post Angular XSS Vulnerability in i18n Handling Exposes Web Applications appeared first on First Hackers News.

Because of this flaw, protected email data may be processed by Copilot and surfaced inside AI chat responses, creating a risk of unintended exposure.

The issue is tracked by Microsoft under reference CW1226324 and was first identified on February 4, 2026. It affects the Copilot “Work Tab” Chat feature.

Vulnerability Details

Technical Cause and Security Impact

Microsoft’s investigation found that a defect in how Copilot processes certain mail folders is responsible for the issue.

Due to this error, emails stored in Sent Items and Drafts can be accessed by Copilot even if confidentiality sensitivity labels are applied.

Normally, sensitivity labels combined with DLP rules should block AI tools from reading or summarizing restricted emails. However, the defect prevents those protections from being properly enforced for the affected folders.

As a result, confidential information may appear in Copilot-generated summaries.

This is especially concerning for sectors such as healthcare, financial services, and government agencies, where strict email protection is tied to regulatory compliance.

The NHS has internally logged the matter as INC46740412, confirming operational impact within public sector environments.

Allowing an AI system to process labeled content despite DLP rules represents a serious breakdown in data governance controls.

Remediation Status

Microsoft began deploying a fix on February 11, 2026, and is contacting certain affected customers to confirm the resolution.

The update is still rolling out, and not all tenants may have received the fix yet.

Organizations using Microsoft 365 Copilot with email sensitivity labels enabled could be impacted until remediation is fully completed.

Recommended Actions

Administrators should monitor the Microsoft 365 Admin Center for updates related to reference CW1226324.

It is also recommended to review Copilot audit logs for unexpected access to labeled email content.

Until Microsoft confirms full deployment of the fix, organizations handling highly sensitive communications may consider temporarily limiting Copilot access to reduce exposure risk.

‍Follow Us on: Linkedin, Instagram, Facebook to get the latest security news!

The post Microsoft 365 Copilot AI Summary Flaw Exposes Emails appeared first on First Hackers News.

The update mainly affects BIG-IP Advanced WAF, NGINX products, and BIG-IP Container Ingress Services. Since these systems often handle incoming application traffic, leaving them unpatched could expose organizations to serious attacks.

All about the vulnerability

BIG-IP Advanced WAF & ASM (CVE-2026-22548)
This flaw affects the Web Application Firewall and Application Security Manager modules on BIG-IP devices. Attackers could potentially bypass security protections or disrupt services. It impacts versions 17.1.0 to 17.1.2, and the fix is included in 17.1.3.

NGINX Vulnerability (CVE-2026-1642)
A major issue was found across the NGINX ecosystem, including NGINX Plus, Open Source, and the Ingress Controller. Because NGINX often runs at the edge of networks as a reverse proxy or load balancer, vulnerable systems could become easy targets. This issue also carries a high severity score.

BIG-IP Container Ingress Services (CVE-2026-22549)
For organizations using Kubernetes or OpenShift, a vulnerability affects Container Ingress Services versions 2.0.0 through 2.20.1. A patched version is available in 2.20.2.

Affected Components

F5 also warned about a configuration risk related to SMTP settings in BIG-IP systems. This isn’t a software bug but could allow misuse if not properly secured. Administrators should review and harden their configurations.

What Organizations Should Do

• Identify all BIG-IP and NGINX systems in use
• Check installed versions against the affected list
• Apply updates as soon as possible
• Review and secure SMTP configurations on BIG-IP devices

Because these products sit at key network entry points, patching them quickly is critical to reducing exposure.

The post Critical Flaws in F5 BIG-IP and NGINX Prompt Urgent Security Patches appeared first on First Hackers News.

Security researchers identified nine separate command injection issues affecting different parts of the router software, including web management, VPN services, cloud communication, and configuration features.

What’s the Core Problem?

The router firmware does not properly validate certain inputs. Because of this, attackers can inject malicious operating system commands through authenticated interfaces.

Most of the vulnerabilities require access from the local network with high privileges. However, one flaw can be triggered remotely by importing a specially crafted configuration file, increasing the risk.

What Could Happen?

If exploited, attackers could:

• Take full administrative control of the router
• Change network settings
• Intercept internet traffic
• Install backdoors for long-term access
• Move deeper into internal networks

This could affect both home users and organizations using the device.

Affected Versions

Vulnerability Overview

Fix Available

TP-Link released firmware version 1.2.4 Build 20251218 that fixes all these issues. Users should update immediately through official TP-Link support channels. Devices left unpatched remain at risk.

The post Security Gaps in TP-Link Devices Expose Users to Full Control Attacks appeared first on First Hackers News.

Security researchers warn that the impact could be widespread, as more than 800,000 telnet services are still directly reachable from the internet. With exploit code now available, the barrier to attack is much lower, increasing the likelihood of large-scale scanning and exploitation.

Why this vulnerability is a serious threat

The flaw allows remote attackers to execute commands on vulnerable systems without authentication. In other words, an attacker does not need valid credentials to gain control.

The root cause is improper input validation in the telnet daemon, which can be abused to bypass security checks and run arbitrary commands on the host.

Telnet itself is a legacy remote access protocol that sends all traffic, including usernames and passwords, in plain text. This has long made it a weak point in network security. When combined with a remote code execution vulnerability, exposed telnet services become extremely high-risk. Attackers can use them not only for initial access, but also for deploying malware, stealing credentials, moving laterally inside networks, or adding compromised systems to botnets.

The release of public exploit code changes the risk level significantly. Threat actors no longer need to develop their own tools, making automated attacks more likely. Internet-wide scans continue to show hundreds of thousands of systems with telnet open on common ports, proving that outdated services are still running in production environments.

Recommended actions for organizations

• Identify all systems exposing Telnet, including port 23 and alternate ports such as 2323
• Immediately disable telnet services on internet-facing systems
• Migrate remote administration to secure alternatives like SSH
• Use firewalls and network segmentation to restrict access to legacy systems that cannot yet be removed
• Monitor logs and network traffic for unusual command execution or unauthorized access attempts
• Prioritize patching and remediation as part of urgent risk reduction efforts

Because the exploit is public and the exposed attack surface is so large, this vulnerability presents a real risk of mass exploitation. Organizations that continue to operate telnet services should act quickly to reduce exposure and prevent potential system compromise.

‍Follow Us on: Linkedin, Instagram, Facebook to get the latest security news!

The post PoC Released for GNU Telnetd RCE, 800K+ Still Exposed appeared first on First Hackers News.

These flaws may expose proxy credentials, database passwords, API keys, and other secrets in production environments.

Vulnerability Summary

Proxy Credentials Exposure via Task Logs

The first issue affects how Apache Airflow handles proxy configurations inside Connection objects. Proxy URLs can include embedded authentication details, such as usernames and passwords.

These proxy fields were not marked as sensitive, which prevented Airflow’s automatic masking from hiding credentials when connections were rendered or logged during task execution. As a result, proxy credentials could appear in plain text within task logs.

Since task logs are often accessible to multiple users and stored in centralized logging systems, this creates a risk of credential misuse and unauthorized access.

The second vulnerability impacts the Rendered Templates section of the Airflow web UI. When templated fields exceed the configured size limit, the masking process may not apply custom secret-masking rules correctly.

This can cause sensitive values, such as API keys or database passwords, to be partially displayed in clear text in the UI. Any user with access to the Airflow web interface could potentially view these exposed values.

Although both issues require authenticated access, they introduce insider-threat risks and can support lateral movement within environments. Long log retention policies can extend exposure if leaked credentials remain stored in archived logs.

Mitigation and Recommendation

Apache Airflow version 3.1.6 resolves both issues by properly classifying proxy fields as sensitive and ensuring secret-masking rules are applied before data is rendered or truncated.

Organizations are strongly advised to upgrade as soon as possible. If immediate upgrades are not feasible, restricting access to task logs and the Airflow web UI can help reduce exposure.

The post Apache Airflow Flaws Risk Exposure of Sensitive Data appeared first on First Hackers News.