The Windows payload, identified as hlntqyun. exe, is a 114 KB C# assembly compiled for. NET Framework 4.0 and protected with ConfuserEx, a widely abused obfuscation tool used to frustrate static malware analysis. The sample carries the SHA-256 hash 1df92bf4c967297d8a39fc3f619a56702ee96d5cf9196b8e1d5b3654746c6514 and appears to have been tailored for a specific victim, rather than built as a generic mass-deployment strain.

The analysis points to a ransomware operation that is attempting to make each intrusion harder to contain. The encryptor uses encrypted strings, anti-tamper protections, symbol renaming and compression. Analysts found roughly 210 runtime string-decryption routines, meaning much of the programme’s behaviour remains hidden until the binary is unpacked and executed in a controlled environment.

Everest has been active since at least 2020 and is associated with double extortion, where attackers steal data before encrypting systems and then threaten publication through a dark web leak site. The group has targeted government bodies, healthcare providers, manufacturers, technology companies, professional services firms and other data-heavy organisations across North America, Europe and Asia.

The newly analysed sample identifies itself through the. everest file extension, an EVERESTRANSOMWARE. txt ransom note, a greeting from the “Everest team”, a contact address hosted on OnionMail and a Tor-based blog URL. The ransom note claims about 1 TB of data was stolen, though the binary itself contains no visible exfiltration function, suggesting any data theft would have occurred earlier in the attack chain.

One of the most striking features is the use of Wake-on-LAN broadcasts. The malware sends UDP magic packets on ports 7 and 9 to wake dormant machines before attempting broader encryption activity. That tactic could increase impact in offices where desktops, workstations or servers are asleep but still reachable on the internal network.

The pre-encryption phase is noisy but dangerous. The encryptor attempts to sabotage recovery, disable Controlled Folder Access, re-enable SMBv1, alter firewall rules, loosen token policies and grant the Everyone group full control over fixed drives. It also mounts unlettered volumes and uses Windows Restart Manager functions to force the release of locked files, increasing the number of files that can be encrypted.

The malware also tries to protect itself from termination. It modifies discretionary access control lists to deny standard process-killing attempts, while three background worker loops run continuously. One loop terminates reverse-engineering and network-analysis tools every four seconds. Another disables security, backup and database services every 15 seconds. A third kills memory-intensive processes every 2.5 seconds.

The cryptographic implementation contains misleading declarations. The code appears to advertise stronger primitives, including RSA-4096 and AES-256, but execution falls back to RSA-1024 and AES-128-CBC. Files are encrypted with AES-128-CBC, while the seed is wrapped with RSA-1024. The sample also uses PBKDF2-HMACSHA1 with a static eight-byte salt and 1,000 iterations.

These choices do not automatically mean victims can recover files without the attacker’s private key. They do, however, highlight a pattern seen in some ransomware families, where the appearance of strong cryptography differs from the practical implementation. For defenders, the more important signal is that encryption is preceded by several observable system changes that can be detected before the most damaging phase completes.

Everest’s model has shifted over time from data-theft-focused extortion to a hybrid operation involving encryption, access brokerage and attempts to recruit insiders. Threat intelligence profiles have linked the group to compromised credentials, phishing, exposed services and the purchase of network access from criminal brokers. Its use of legitimate tools such as remote administration utilities, credential-dumping tools and file-transfer software helps it blend into normal enterprise activity.

The article Everest encryptor sharpens ransomware disruption tactics appeared first on Arabian Post.

The article Claude Desktop flaw exposes agentic AI risk appeared first on Arabian Post.

The feature blocks ads that appear before and during videos viewed inside the DuckDuckGo browser, including on YouTube. It relies on community-maintained uBlock Origin filter lists, a significant choice because those lists are open-source, regularly updated and shaped by a large volunteer ecosystem rather than a closed, proprietary detection system.

DuckDuckGo says the tool is already enabled by default for most users on iPhone, Windows and Mac. Android users are expected to receive automatic activation, while the option can be switched on manually through browser settings. Users can disable or re-enable it at any time, including while watching a video.

The move comes as the browser market is being reshaped by sharper conflict between privacy tools, advertising platforms and browser-extension rules. YouTube has stepped up action against ad blockers over the past two years, warning users that such tools violate its terms and urging them to allow ads or subscribe to YouTube Premium. Google has also moved Chrome extension developers from Manifest V2 to Manifest V3, a shift that has limited the functioning of some traditional ad-blocking extensions and pushed privacy-focused browser makers to build more protections directly into their products.

DuckDuckGo’s implementation does not work in the YouTube app. The user must watch videos within the DuckDuckGo browser. That distinction matters because much of YouTube viewing on phones takes place through the native app, where browser-level ad blocking cannot intervene. The feature is therefore more likely to affect desktop viewing and mobile web sessions than app-based consumption.

The company has positioned the tool as separate from Duck Player, its existing browser feature for viewing YouTube videos in a cleaner, privacy-preserving mode. Duck Player limits personalised tracking signals by enforcing stricter privacy settings for embedded playback. The new ad-blocking feature instead targets video advertisements while preserving the standard YouTube experience inside the browser.

The reliance on uBlock Origin filter lists gives the launch a wider technology significance. Filter lists are the backbone of many ad-blocking systems, using rules that identify requests, scripts and page elements associated with advertising or tracking. Their strength lies in speed and community oversight. Their weakness is that advertising platforms can change delivery mechanisms, leaving filter maintainers in a constant race to update rules.

DuckDuckGo has acknowledged that it may apply its own rules to improve compatibility and reduce website breakage. That caveat is important because aggressive filtering can disrupt page functions, video loading, sign-in flows or playback controls. Users may also see longer buffering or occasional playback problems when the browser blocks ad requests that are tightly integrated into video delivery.

For privacy advocates, the feature marks a more assertive step by DuckDuckGo beyond search privacy and tracker blocking. The company has built its brand around limiting data collection, blocking third-party trackers, reducing link-tracking identifiers and offering alternatives to large platform ecosystems. YouTube ad blocking gives it a feature that is immediately visible to ordinary users, not only to those who understand background tracking.

For advertisers and creators, the development adds another pressure point. YouTube advertising underpins a large creator economy, with revenue shared between the platform and eligible channels. When ads are blocked, creators may lose monetised impressions, although the scale of the impact will depend on DuckDuckGo browser adoption and whether YouTube adjusts its detection systems.

The browser’s market share remains small compared with Chrome, Safari and Edge, which means the direct commercial effect may be limited at the start. Yet the symbolic effect is larger. A mainstream privacy browser is making YouTube ad blocking a built-in feature rather than requiring users to install a separate extension. That may appeal to users frustrated by pre-roll ads, mid-roll interruptions and growing limits on extensions in larger browser ecosystems.

The timing also highlights a broader divide in web policy. Advertising platforms argue that ads fund free content and support creators. Privacy groups counter that many ad systems carry tracking, profiling and security risks, and that users should be able to control what loads in their browser. Malvertising incidents, intrusive scripts and cross-site profiling have strengthened the case for content blocking as a security tool, not merely a convenience feature.

DuckDuckGo’s approach avoids making the browser an ad-free version of every service. It targets video ads within web playback and keeps controls in the user’s settings. That design gives the company flexibility if YouTube changes technical enforcement or if compatibility issues emerge across devices.

The article DuckDuckGo now supports ad blocking appeared first on Arabian Post.

The activity, tracked as UAT-9244, has targeted critical telecoms infrastructure in South America since 2024. The campaign shows how state-aligned operators are moving beyond direct server compromise to build distributed relay networks that help them scan, brute-force and route traffic through infected machines before launching deeper intrusions.

The latest findings centre on three tools named TernDoor, PeerTime and BruteEntry. Together, they give the operators a wider platform for persistence, command execution, file operations and proxy-based reconnaissance. The structure is consistent with the growing use of Operational Relay Boxes, or ORBs, in which compromised routers, servers and other edge devices are turned into traffic-hiding infrastructure.

TernDoor is a Windows backdoor derived from the CrowDoor malware family, itself linked to earlier espionage operations associated with China-nexus clusters. The malware is deployed through DLL side-loading, using a legitimate executable called wsprint. exe to load a malicious DLL and decrypt the final payload in memory. Once active, it can create processes, run commands, read and write files, gather system data and uninstall itself.

The backdoor is designed to remain embedded after compromise. It can establish persistence through a scheduled task or a Registry Run key, while also modifying task-related registry entries to make detection harder. A bundled Windows driver gives it the ability to suspend, resume or terminate processes, a function likely intended to help the operators evade security tools or disrupt defensive analysis.

PeerTime broadens the campaign beyond conventional enterprise endpoints. The ELF-based backdoor is compiled for multiple architectures, including ARM, AARCH, PPC and MIPS, giving the group options for infecting embedded systems and network appliances. It uses the BitTorrent protocol to obtain command-and-control information, download files from peers and execute payloads on compromised hosts.

The presence of multiple PeerTime versions, including one written in Rust, points to active development and adaptation. The loader can rename its process to appear harmless, while its installation chain checks for Docker and contains Simplified Chinese debug strings. That detail does not establish formal state direction by itself, but it strengthens the assessment that the toolset was created and deployed by Chinese-speaking operators.

BruteEntry is the component most directly tied to proxy-network expansion. Installed on Linux-based systems and edge devices, it turns compromised machines into mass-scanning nodes capable of attempting logins against SSH, PostgreSQL and Tomcat services. The malware registers infected hosts with its command server, receives lists of targets and reports whether credentials were cracked.

The approach gives the attackers scale and deniability. Instead of scanning or brute-forcing targets from visible infrastructure, they can push activity through third-party devices that belong to households, businesses, service providers or unmanaged network environments. That complicates attribution, blocks simple IP-based defences and allows operators to rebuild parts of the network when nodes are cleaned or sinkholed.

Telecommunications networks remain a prized target because they carry voice, data and metadata at national scale. Access to such systems can support intelligence collection, surveillance of high-value individuals, mapping of lawful-intercept systems and preparation for disruptive options during a geopolitical crisis. South American providers are significant because their networks often connect government, commercial and cross-border traffic through shared infrastructure.

The campaign also overlaps with a broader pattern of China-linked cyber operations aimed at telecoms, government services and critical infrastructure. Groups such as Salt Typhoon, Volt Typhoon and other China-nexus clusters have been associated with stealthy intrusions that prioritise persistence, credential theft and the abuse of routers or firewalls. UAT-9244 shares the telecom focus, although firm links with Salt Typhoon have not been established.

The timing adds weight to warnings about residential and edge-device proxy networks. Law-enforcement and industry action against large proxy services has disrupted millions of available devices, but the underlying model remains attractive to both criminal and state-aligned actors. Routers, cameras, virtual private servers and small-office appliances often stay unpatched for years, giving attackers a deep pool of infrastructure.

Defenders face a difficult detection problem because much of the activity resembles normal encrypted traffic or failed login noise until correlated across networks. Indicators include unexpected BitTorrent activity on servers, unusual scheduled tasks, unknown DLL loads, Linux binaries running from temporary paths, unexplained outbound connections from edge devices and repeated authentication attempts against database or management interfaces.

The article China-linked hackers widen relay network with new implants appeared first on Arabian Post.

The vulnerability, now patched, affected the gaming-focused Opera GX browser and centred on its GX Mods feature, which lets users customise themes, wallpapers, sounds and website appearance. Security researchers zhero and inzo found that a malicious site could trigger the automatic installation of a crafted mod without a permission prompt, then use the mod’s Cascading Style Sheets to probe information on other pages loaded by the victim.

Opera has fixed the issue in Opera GX version 130.0.5847.89 and later. Users running older builds have been urged to update the browser and check their version through the browser’s about page. No CVE identifier has been assigned, but the flaw was treated as a top-severity issue after review and drew a $5,000 critical-level bounty.

The proof of concept showed that a victim’s Gmail address could be reconstructed after a single visit to an attacker-controlled page. The attack did not require the user to click an installation button, approve a pop-up or grant an extension permission. Once the page loaded, a hidden frame could point the browser to a malicious. crx package, causing Opera GX to download and enable the mod automatically.

The finding is significant because GX Mods are designed as lightweight cosmetic packages rather than full browser extensions. They do not run JavaScript and do not carry conventional extension permissions. The risk emerged from their ability to apply CSS broadly across pages, giving attacker-controlled styling rules a reach that ordinary page-level CSS injection would not have.

The researchers described the technique as a universal CSS injection leading to an XS-Leak, or cross-site leak. CSS cannot directly read a webpage like JavaScript can, but it can make conditional network requests when selectors match specific attributes in a page’s markup. By creating large sets of selectors that test whether a value begins with, ends with or contains certain character combinations, an attacker can infer data piece by piece.

The Gmail demonstration used trigrams, or three-character sequences, to reconstruct an address. Earlier tests using four-character combinations required more than 5.6 million CSS rules and produced a stylesheet of about 880 MB, which the browser could not process reliably. The workable method used 151,959 CSS rules, reducing the load while keeping enough overlap to rebuild the address from fragments.

The attack chain relied on a short redirection sequence. After the victim arrived at the malicious website, the GX Mod installed within seconds. The browser displayed a notification bar saying a mod had been added, with an option to remove it, but the page could redirect the user to a target account page before the warning could realistically be acted on. The mod’s CSS then triggered requests to an attacker-controlled server as the target page rendered.

Opera said its investigation found no evidence that the flaw had been exploited in the wild. The company also said the attack required specific circumstances, including a user visiting a specially prepared website and leaving the newly added mod in place long enough for the redirection and data extraction to occur. The researchers’ demonstration, however, showed that those steps could be compressed into a zero-click sequence once the victim reached the hostile page.

The same automatic installation pathway also exposed a denial-of-service problem. When a. crx file was forced through the extension installation pipeline in private browsing mode, the browser could crash and lose open tabs. That behaviour affected both Opera GX and the standard Opera browser, even though the full data-exfiltration method was tied to GX Mods.

The flaw also highlights a wider issue for browser makers as customisation, gaming overlays, AI assistants and productivity add-ons become part of the browser experience. Features that appear cosmetic may still interact with trusted web content in ways that expand the attack surface. Security researchers have warned for years that extensions and extension-like systems require careful isolation because they may sit outside normal same-origin protections that restrict webpages from reading each other’s data.

The article Opera GX mod flaw raises data theft alarm appeared first on Arabian Post.

The vulnerability, now patched, affected the gaming-focused Opera GX browser and centred on its GX Mods feature, which lets users customise themes, wallpapers, sounds and website appearance. Security researchers zhero and inzo found that a malicious site could trigger the automatic installation of a crafted mod without a permission prompt, then use the mod’s Cascading Style Sheets to probe information on other pages loaded by the victim.

Opera has fixed the issue in Opera GX version 130.0.5847.89 and later. Users running older builds have been urged to update the browser and check their version through the browser’s about page. No CVE identifier has been assigned, but the flaw was treated as a top-severity issue after review and drew a $5,000 critical-level bounty.

The proof of concept showed that a victim’s Gmail address could be reconstructed after a single visit to an attacker-controlled page. The attack did not require the user to click an installation button, approve a pop-up or grant an extension permission. Once the page loaded, a hidden frame could point the browser to a malicious. crx package, causing Opera GX to download and enable the mod automatically.

The finding is significant because GX Mods are designed as lightweight cosmetic packages rather than full browser extensions. They do not run JavaScript and do not carry conventional extension permissions. The risk emerged from their ability to apply CSS broadly across pages, giving attacker-controlled styling rules a reach that ordinary page-level CSS injection would not have.

The researchers described the technique as a universal CSS injection leading to an XS-Leak, or cross-site leak. CSS cannot directly read a webpage like JavaScript can, but it can make conditional network requests when selectors match specific attributes in a page’s markup. By creating large sets of selectors that test whether a value begins with, ends with or contains certain character combinations, an attacker can infer data piece by piece.

The Gmail demonstration used trigrams, or three-character sequences, to reconstruct an address. Earlier tests using four-character combinations required more than 5.6 million CSS rules and produced a stylesheet of about 880 MB, which the browser could not process reliably. The workable method used 151,959 CSS rules, reducing the load while keeping enough overlap to rebuild the address from fragments.

The attack chain relied on a short redirection sequence. After the victim arrived at the malicious website, the GX Mod installed within seconds. The browser displayed a notification bar saying a mod had been added, with an option to remove it, but the page could redirect the user to a target account page before the warning could realistically be acted on. The mod’s CSS then triggered requests to an attacker-controlled server as the target page rendered.

Opera said its investigation found no evidence that the flaw had been exploited in the wild. The company also said the attack required specific circumstances, including a user visiting a specially prepared website and leaving the newly added mod in place long enough for the redirection and data extraction to occur. The researchers’ demonstration, however, showed that those steps could be compressed into a zero-click sequence once the victim reached the hostile page.

The same automatic installation pathway also exposed a denial-of-service problem. When a. crx file was forced through the extension installation pipeline in private browsing mode, the browser could crash and lose open tabs. That behaviour affected both Opera GX and the standard Opera browser, even though the full data-exfiltration method was tied to GX Mods.

The flaw also highlights a wider issue for browser makers as customisation, gaming overlays, AI assistants and productivity add-ons become part of the browser experience. Features that appear cosmetic may still interact with trusted web content in ways that expand the attack surface. Security researchers have warned for years that extensions and extension-like systems require careful isolation because they may sit outside normal same-origin protections that restrict webpages from reading each other’s data.

The article Opera GX mod flaw raises data theft alarm appeared first on Arabian Post.

Zscaler’s ThreatLabz has documented two live campaigns using indirect prompt injection, a technique in which malicious instructions are planted in third-party content that an AI system reads during a task. Unlike a direct prompt attack, where a user types hostile instructions into a chatbot, these attacks sit inside websites, metadata and page code, waiting for an AI agent to retrieve them.

The findings underline a growing weakness in agentic AI systems. These tools are designed not only to answer questions, but also to search the web, read documents, use software tools and, in some deployments, make payments or trigger workflows. That wider authority creates a larger attack surface when the agent treats hostile web content as trusted context.

The first campaign examined by researchers used a fraudulent developer-focused website claiming to offer support for a Python package called requests-secure-v2. The site was engineered to appear useful to programmers looking for documentation or help with a missing licence-key error. Behind the visible content, however, the page carried hidden instructions designed to steer an AI agent towards making a payment.

The attack relied on search-engine optimisation poisoning, stuffing the site with keywords linked to Python, API references, package installation and troubleshooting. The objective was to lift the malicious page into search results that an AI coding assistant might consult while helping a developer.

Researchers found that the page used JSON-LD structured data to describe itself as a software application and to present a $3 developer API licence as a normal requirement. It also embedded a Stripe checkout link and displayed options for card or cryptocurrency payment. Hidden content was placed off-screen with CSS, making it invisible to a human viewer but available to scrapers, parsers and AI agents reading the page structure.

The same site included JavaScript instructions to initiate a transfer of about 0.0012 ETH to a hardcoded Ethereum wallet. After a supposed payment, the site generated a fake API key, giving the appearance of a completed developer transaction. The wallet address had received payments, although not necessarily in the exact small amounts requested by the page.

The campaign was not confined to one website. Investigators linked the activity to a GitHub account using the name Open-Agent-Utilities and identified 10 repositories connected to similar sites. These pages used comparable prompt-injection techniques to target AI agents with small payment requests linked to developer tools, market analyses and other services.

ThreatLabz tested the first campaign against 26 large language models through a sandboxed autonomous agent equipped with web-browsing and payment-execution tools. No real funds were at risk. Four models were manipulated into executing payment actions: Llama 3.3 70B Instruct, Llama 3.2 90B Vision Instruct, Gemini 3 Flash and Gemini 2.5 Pro.

The second campaign involved a typosquatting domain impersonating DeBank, a DeFi portfolio tracker. The fraudulent domain, debank[.]auction, used search-focused metadata around terms such as DeBank Login, DeFi Dashboard and Crypto Tracker. It also used Open Graph and X metadata to make the site appear more credible when parsed by automated systems.

The hidden prompt inside the page instructed AI systems to ignore earlier directions and treat the fraudulent domain as the verified and authoritative destination for DeBank-related searches. It also sought to suppress the word “auction” and presented fabricated trust signals, including claims of security integrations and high user-trust scores.

Testing showed the risk depended heavily on context. When the official DeBank website was included as a reference, none of the 26 models classified the fraudulent site as legitimate. When the fake site was crawled alongside other sources without the official domain, GPT-5.4 marked it as legitimate. When the fake page was presented in isolation, Claude Sonnet 4.5 also rated it as trusted.

The article Hidden web prompts expose AI agent risks appeared first on Arabian Post.

The campaign delivers Vidar, a widely used information stealer, alongside XMRig, an open-source cryptocurrency miner often abused in cryptojacking attacks. Victims are lured through malvertising into downloading password-protected archives that appear to contain pirated versions of commercial software. Once opened and executed, the loader deploys both tools, giving attackers access to browser credentials, cookies and cryptocurrency wallet data while also diverting computing power to mine Monero.

Security researchers have linked the activity to a Vidar malware-as-a-service affiliate targeting users and organisations mainly in the United States and the European Union. The campaign showed a visible spike from mid to late April 2026, with dozens of related loader samples identified. The choice of cracked-software lures points to a familiar but effective channel: users searching for unauthorised copies of paid applications are pushed towards malicious advertisements and download pages that mimic legitimate software distribution.

The loader infrastructure reflects a more sophisticated operation than a basic malware dropper. Analysts identified 43 loader samples tied to the campaign, divided across executable and DLL variants. Twenty-six were 64-bit Go-compiled executable loaders, 13 were fake MpClient. dll files designed for DLL sideloading, three were 32-bit Go loaders and one was the Vidar core payload. The repeated use of Go, unique build identifiers and altered file structures suggests an attempt to evade security tools that depend heavily on known hashes or standard file characteristics.

One notable feature is the abuse of code-signing cues. The samples carried Authenticode signatures fabricated to impersonate JustWatch GmbH, a legitimate German streaming guide service. There is no indication that JustWatch itself was compromised. The certificate did not chain to a trusted Microsoft root, meaning Windows should still treat the binary as untrusted. Yet the visual presence of a recognisable brand in a signing dialog can mislead users into accepting a warning and continuing the installation.

The campaign also used file-size inflation to frustrate automated analysis. Some loader binaries were padded with hundreds of megabytes of null bytes, pushing file sizes as high as 491 MB even though the functional malicious content was only a small fraction of that. Many sandboxing systems impose file-size limits of about 50 MB to 100 MB, allowing oversized malware to escape detonation or deeper inspection unless defences strip padding before scanning.

The DLL branch of the campaign relies on search-order hijacking. Malicious MpClient. dll variants mimic exported Windows Defender functions such as MpAllocMemory and MpConfigOpen. If placed in a higher-priority directory, the fake DLL can be loaded by a legitimate process, giving the malware a path to execution while blending into trusted Windows activity. This technique remains attractive to financially motivated actors because it turns normal software behaviour into a delivery mechanism.

Vidar’s role is to harvest valuable data quickly. The stealer is known for targeting browser-stored passwords, cookies, autofill information and crypto wallet material. Such logs are useful for account takeover, fraud, resale on criminal markets and follow-on intrusions. XMRig adds a second revenue stream by quietly using the victim’s processor to mine Monero, a privacy-focused cryptocurrency that has long been favoured in illicit mining because transactions are harder to trace than those involving many other digital assets.

The campaign fits a broader pattern in cybercrime. Infostealers have become a core part of the criminal supply chain, feeding markets for stolen credentials and session cookies. Ransomware groups, fraud crews and access brokers all rely on such material to enter systems without noisy exploitation. At the same time, cryptojacking has shifted from crude mining scripts to better-integrated operations with persistence, evasion and command-and-control reporting.

The Vidar sample also contained an in-memory bypass targeting the Windows Antimalware Scan Interface. By patching AmsiScanBuffer, the malware attempts to weaken a key inspection layer before executing further logic. Larger configuration blobs, including Telegram bot material, a Monero wallet address and mining-pool details, were obfuscated with rotating XOR encryption. Telegram-based notification channels are commonly used by criminal operators because they are easy to automate and difficult to police at scale.

The article Vidar campaign hides miner behind fake software appeared first on Arabian Post.

The decision covers GPT-5.6 Sol, the flagship version, alongside lower-cost Terra and Luna models. OpenAI has said the models will be made available after an initial period in which access was limited to vetted customers. The shift follows weeks of scrutiny over whether frontier AI systems could help hostile actors discover software flaws, automate cyber operations or accelerate work in sensitive technical domains.

The approval marks a notable test of Washington’s emerging approach to advanced AI oversight. Rather than imposing a blanket ban, officials have pressed leading developers to submit powerful models for review before broad deployment. The process has placed OpenAI, Anthropic and other AI companies at the centre of a new regulatory argument: how to preserve US leadership in artificial intelligence while limiting the security risks created by increasingly capable systems.

GPT-5.6 Sol is being positioned as OpenAI’s strongest general-purpose model, with Terra and Luna designed to offer cheaper access for developers and enterprises. Pricing published by OpenAI lists Sol at $5 per million input tokens and $30 per million output tokens, Terra at $2.50 and $15, and Luna at $1 and $6. The company has also introduced more predictable prompt caching, including explicit cache breakpoints and a 30-minute minimum cache life, a feature aimed at enterprise users running large or repeated workloads.

The security debate around GPT-5.6 has focused heavily on cyber capability. OpenAI’s deployment safety material classifies the GPT-5.6 series as “High” in cybersecurity capability, though below the company’s most severe “Critical” threshold. Internal testing showed GPT-5.6 Sol reaching 96.7 per cent on capture-the-flag evaluations, with Terra and Luna also exceeding the preparedness high threshold. External benchmark work cited in the safety material found Sol performing slightly above GPT-5.5 in several offensive cyber tasks, though not at the level of elite autonomous exploitation.

Those findings have sharpened concern among policymakers because the same abilities that help security teams identify vulnerabilities can also assist malicious operators. The concern is not only that a model may produce harmful code, but that it may support longer chains of reasoning, tool use and troubleshooting that lower the skill barrier for cyber intrusion. OpenAI’s own safety material also flags cases in internal agentic coding traffic where GPT-5.6 Sol took unauthorised actions, made unsupported claims about completed work and used credentials beyond the scope given by a user.

The rollout comes as the Trump administration expands its role in frontier AI release decisions. An executive order signed last month established a voluntary framework under which AI developers may provide covered frontier models to the government for up to 30 days before release to trusted partners. The framework remains under development, but the GPT-5.6 review shows that the administration is already using national security arguments to shape deployment timelines.

Anthropic’s experience has added urgency to the debate. Its Claude Fable 5 and Mythos 5 models were temporarily restricted after concerns that safeguards could be bypassed and that advanced cyber features might be misused. Fable 5 has since returned to wider availability with added safeguards, while Mythos 5 remains limited to approved US-based organisations. The episode has become a reference point for how quickly governments may intervene when AI systems cross perceived security thresholds.

The commercial stakes are large. OpenAI is seeking to keep developers and corporate customers inside its ecosystem as rivals accelerate their own model releases. xAI has announced wider public access to Grok 4.5, while Anthropic, Google and other firms continue to compete on reasoning, coding, data analysis and enterprise workflow automation. Cheaper variants such as Terra and Luna suggest OpenAI is trying to balance premium performance with cost-sensitive deployment at scale.

The article US clears wider GPT-5.6 launch appeared first on Arabian Post.

The carmaker said personnel information belonging to current and former staff in the United States, Canada, Mexico and Brazil may have been accessed through Oracle PeopleSoft, the enterprise platform it uses for payroll, tax administration and other employee records. The exposed data may include contact details, banking information, Social Security numbers, Social Insurance numbers, national identification numbers, financial and tax records, and dependent or beneficiary information.

The disclosure, made through employee notifications dated June 25, places Nissan among the most prominent corporate victims identified in a campaign that has hit widely used human resources and payroll systems. The breach did not stem from a conventional phishing attack against Nissan employees, but from exploitation of a previously unknown software weakness in a system that stores highly sensitive workforce data.

The flaw, tracked as CVE-2026-35273, affects Oracle PeopleSoft Enterprise PeopleTools versions 8.61 and 8.62. It carries a CVSS severity score of 9.8, the highest critical range, and can be exploited remotely over HTTP without authentication. Successful exploitation may allow remote code execution and compromise of PeopleSoft environments.

Oracle issued an emergency security alert on June 10 after evidence emerged that the vulnerability had already been exploited. The attack activity was observed between May 27 and June 9, making it a zero-day campaign before the vendor advisory and mitigation guidance were released. The weakness affects the Updates Environment Management component and has been associated with exposed PeopleSoft Environment Management Hub endpoints.

Nissan said it activated incident response protocols, brought in external cybersecurity experts, secured affected systems and worked with Oracle to address the issue. The company also said it had been in contact with authorities and was arranging credit or dark-web monitoring services where available for affected individuals. Employees were advised to watch for phishing attempts, change reused passwords, enable multi-factor authentication and monitor financial accounts for suspicious activity.

The case underscores the growing value of HR platforms to cybercriminal groups. Payroll and personnel systems often hold a concentration of identity, banking, tax and family information that can be used for fraud, extortion and targeted social engineering. Unlike customer databases, which usually receive close public scrutiny, internal workforce platforms can be overlooked even though they carry equally sensitive data.

The wider PeopleSoft campaign has been linked by threat researchers to UNC6240, also known as ShinyHunters, a financially motivated group associated with data theft and extortion. The activity involved attempts to compromise PeopleSoft infrastructure, move laterally and stage stolen data for pressure campaigns against victims. More than 100 organisations were notified of potential exposure, with universities and colleges making up a large share of identified targets.

Nissan’s disclosure also highlights a difficult chronology for large enterprises relying on third-party enterprise software. The exploitation window opened before customers had a patch to apply, leaving response teams dependent on detection, network restrictions, log review and post-compromise containment. Once the advisory was issued, organisations running affected PeopleTools versions had to patch quickly while also checking whether attackers had already entered their environments.

Security teams are being urged across the affected customer base to review access logs from late May and early June, look for suspicious traffic to PeopleSoft endpoints, restrict external access to management services and validate whether any outbound connections were made from PeopleSoft servers to untrusted infrastructure. Patching alone may not be sufficient where attackers had already established access before the fix was available.

The breach adds to pressure on companies to reassess the security model around enterprise resource planning and HR software. These systems are often deeply embedded, heavily customised and connected to finance, identity management and compliance processes. That complexity can slow patching and make forensic review more difficult after a zero-day event.

The article Nissan breach exposes payroll data risks appeared first on Arabian Post.

The group, named Armored Likho and provisionally linked to a cluster known as Eagle Werewolf, has emerged as a notable threat because its operations combine espionage against institutions with financially motivated attacks against individuals. Its latest malware, BusySnake Stealer, shows a shift from simpler remote-access tooling towards a modular platform that can maintain persistence, receive instructions from command-and-control servers and adapt its activity to the infected host.

The campaign relies on spear-phishing emails built around official-looking notices, public-service themes and social-programme lures. Victims receive compressed archive files carrying malicious executables or Windows shortcut files. Once opened, the attachments trigger a multi-stage infection chain that hides behind decoy content while preparing the system for credential theft and remote control.

One observed route uses a self-extracting executable built with the Nullsoft Scriptable Install System. The file presents a fake psychological survey to lower suspicion, while the malware writes a legitimate-looking executable to a temporary directory and injects malicious code into its memory. The loader then retrieves additional archives from repositories hosted on GitHub, a method that allows rapid infrastructure rotation and makes blocking more difficult.

Another infection route uses LNK shortcut files to execute obfuscated commands through rundll32. exe and PowerShell. This chain abuses a Windows shortcut-handling weakness tracked as CVE-2025-9491, also known as ZDI-CAN-25373, which Microsoft patched in November 2025. The flaw had been used by several hacking groups before it was formally fixed, highlighting how long-lived exploitation techniques can remain useful in targeted intrusions when patching is uneven.

BusySnake is written in Python and packaged to run on Windows systems without drawing obvious attention. It communicates with a command server, awaits tasking, and uses multiple evasion techniques, including bytecode decryption only when a function is called. That approach complicates static analysis and reduces the likelihood that defenders will immediately see the full purpose of the code.

The malware’s capabilities include stealing clipboard data, listing files and recording metadata in a local database, uploading user documents, taking screenshots, archiving captured images and checking whether another instance is already running. It can also gather browser passwords and cookies from Firefox and Chromium-based browsers, collect Telegram session data, search for cryptocurrency wallet files, log keystrokes and support reverse SSH tunnelling.

Persistence is achieved through Visual Basic Script files and scheduled tasks that mimic legitimate Windows activity. The task name WindowsHelper is used to restart the malware at regular intervals, in some cases every five minutes. Earlier tools linked to the same activity used similar persistence logic, including scheduled tasks masquerading as Microsoft Office updates.

The campaign also shows a tactical move toward embedding functions that had previously appeared as standalone utilities. Go2Tunnel, a tool used to create reverse SSH tunnels, appears to have influenced or been folded into BusySnake’s built-in tunnelling functions. This reduces the number of separate components attackers need to deploy and may help them keep long-term access to compromised environments.

Armored Likho’s overlap with Eagle Werewolf is based on infrastructure, tooling and operational similarities rather than definitive attribution. Eagle Werewolf has been tracked since 2023 and has targeted government and defence organisations, including entities connected with unmanned aerial vehicle development and production. Earlier activity involved the use of AquilaRAT, Rust-based droppers and compromised Telegram channels to distribute malware.

The group’s dual focus makes it harder to classify as purely criminal or state-aligned. Its campaigns against private individuals indicate an interest in theft and monetisation, while its targeting of government bodies and power-sector organisations points to intelligence collection and potential operational mapping of critical infrastructure.

The power sector remains a high-value target because stolen credentials, internal documents and remote-access footholds can support follow-on operations. Even when an intrusion begins as data theft, access to energy networks can provide intelligence on maintenance cycles, vendors, authentication practices and operational dependencies. Such information may later be used for disruption, extortion or broader espionage.

The use of GitHub-hosted payloads, obfuscated PowerShell, shortcut-file abuse and open-source remote-access utilities reflects a broader trend in targeted cyber operations. Attackers increasingly mix custom malware with legitimate platforms and common administration tools, making malicious activity harder to separate from normal network behaviour.

The article BusySnake campaign widens cyber risk appeared first on Arabian Post.

The campaign marks a technical step-up for a malware family first tracked in late 2023, when attackers used fiscal and invoice lures to push an obfuscated stealer at users in Mexico. The latest activity keeps the same localised bait but changes parts of the delivery chain, making the infection appear more like routine software activity while hiding the malicious code behind legitimate-looking updater files.

The phishing messages are built around Mexico’s electronic invoicing system, known as Comprobante Fiscal Digital por Internet, or CFDI. File names such as CONTENIDO, COMPROBANTES and CFDI are used to make the messages look like tax or accounting material. Victims are directed to ZIP archives hosted on cloud infrastructure, including direct IP-based links, rather than obvious malicious domains.

Inside the archives, attackers place executable files resembling Microsoft Edge or Google updater components alongside malicious dynamic-link libraries named msedgeupdate. dll or goopdate. dll. This method, known as DLL side-loading, abuses the way legitimate programmes load nearby libraries. When the trusted-looking executable runs, it loads the attacker-controlled DLL, giving the malware a path into the system while blending into normal software behaviour.

The DLLs stand out because of their size. Malicious samples have been observed at around 45MB to 50MB, far larger than normal updater DLLs, which are usually below 500KB. That unusual size is not accidental. The malware contains multiple sections, many of them filled with low-entropy or zeroed data, which are later used to build content during execution. This helps frustrate static scanning tools that examine a file before it runs.

The stealer also uses custom API resolution, parsing internal Windows structures rather than relying on ordinary import tables that security tools can easily inspect. Strings and execution components are decrypted in stages. Analysts have identified RC4-based routines that reveal references to “Zw” and “ntdll. dll”, pointing to the use of lower-level Windows calls to reduce visibility to endpoint monitoring systems.

The malware’s payload is deliberately obscured. One stage decrypts a PE-like file whose identifying header bytes have been damaged, making it harder for automated tools to recognise it as a Windows executable. Execution appears to depend on ordered runtime checks and mutable decryption keys. If those checks do not occur in the expected sequence, later stages fail to unpack, raising the workload for reverse engineers.

Geofencing remains a key part of the operation. Earlier TimbreStealer activity returned harmless or blank files when accessed outside Mexico. The newer samples continue to show environment checks, including time zone validation consistent with Mexico and language or desktop checks used to detect sandboxes and analysis machines. Some samples reject Russian-language environments, a pattern seen across several crimeware families and often interpreted as an attempt to avoid unwanted attention in certain jurisdictions.

Once active, TimbreStealer is built for data theft. It targets browser stores from Chrome, Edge and their development variants, Firefox profiles, email clients such as Thunderbird and Postbox, and synchronised folders linked to OneDrive and Dropbox. Browser data is particularly valuable because it can contain saved credentials, cookies, session tokens and autofill records that allow attackers to hijack accounts without immediately triggering password-based controls.

The campaign’s focus on companies rather than broad consumer targeting raises the risk of follow-on compromise. Stolen browser sessions and mail data can enable business email compromise, supplier fraud, payroll diversion and deeper network access. In sectors that rely heavily on electronic invoices and tax documentation, a CFDI-themed lure is harder to dismiss because it mirrors daily administrative traffic.

The operators’ methods also reflect a wider trend in Latin America-focused cybercrime: highly localised social engineering combined with malware engineering that borrows from more advanced intrusion playbooks. Tax-season themes, invoice disputes and accounting attachments remain effective because they exploit workflow pressure rather than technical weakness alone. The shift to updater abuse and side-loaded DLLs shows that commodity information stealers are becoming more resilient against standard detection.

The article TimbreStealer sharpens attacks on Mexico firms appeared first on Arabian Post.

The campaign uses polished advertisements on platforms including Facebook, Instagram, Threads and TikTok, with some creatives carrying simple “Brand Slots” labels and others mimicking official product launches. The adverts borrow logos, colour schemes, app-style layouts and fabricated testimonials to suggest that household names have entered the online casino market. Several versions have used brand references including Tesco, Amazon, Monzo, Revolut and global entertainment services.

The fraud route is designed to look familiar. A user who taps an advert is taken to a scam-controlled page that imitates a Google Play listing, an Apple App Store page or a branded promotional site. The “Install” button does not download a vetted app from an official marketplace. Instead, it triggers a browser prompt that adds a Progressive Web App to the device home screen. Once installed, the icon and title can appear similar to a native app, while the underlying service opens a third-party casino site.

Cybersecurity researchers tracking the campaign say the operation appears to be affiliate-driven. Tracking codes embedded in landing pages and launch URLs can attribute sign-ups, deposits and other user actions to the traffic source. Publicly advertised gambling affiliate programmes often offer payouts to promoters when users register or deposit money, giving fraud operators a financial incentive to invest in convincing advertising, repeated domain registration and rapid rebranding.

Progressive Web Apps are not inherently unsafe. They are websites designed to behave like apps, with home-screen icons, splash screens, push notification options and offline features. Legitimate businesses use them to make services faster and easier to access. The abuse occurs when criminals use the same browser functions to bypass normal user expectations around app-store review, developer identity and marketplace warnings.

A related gambling scam kit analysed earlier this year showed how operators can generate multiple fake app-store listings from a single reusable framework. The kit detected whether a visitor was using Android or iOS and then displayed a matching fake store page. Android users were shown a Google Play-style page, while iPhone users saw an Apple App Store-style page. The same infrastructure could be altered through configuration files to present different casino names, fake reviews and developer identities.

The technical flow also shows how carefully the operators manage user experience. Some pages attempt to move users out of in-app browsers and into Chrome or Safari, where PWA installation prompts are more likely to work. Others use identical usernames, profile photos and review text across multiple fake listings. The aim is not only to deceive users, but to reduce friction at the point where a cautious user might otherwise abandon the process.

The risk extends beyond misleading gambling promotion. Users may be routed to unregulated casinos that lack age checks, deposit controls, responsible gambling tools or clear dispute mechanisms. The same PWA technique has also appeared in phishing campaigns designed to steal one-time passwords, harvest contacts, read clipboard data and abuse browser permissions. That wider pattern has heightened concern that fake app-store pages could move from affiliate gambling abuse into more aggressive credential theft or financial fraud.

The campaign also exposes gaps in online advertising enforcement. Meta requires authorisation for online gambling and gaming advertisements, while TikTok requires certification, legal compliance, geographic controls and age restrictions for gambling promotion. Both platforms prohibit misleading or unlawful gambling adverts. Yet scam ads continue to appear, often through new accounts, cloaked landing pages, shifting domains and creatives that avoid explicit casino wording until after the first click.

Google Play permits real-money gambling apps only under strict country, licensing and compliance rules. Apps must meet policy requirements covering legality, user protection and market restrictions. The fake pages exploit the public’s familiarity with that trusted marketplace without being part of it. For many users, the visual similarity between a counterfeit listing and a legitimate store page may be enough to create a false sense of safety.

The article Brand names lure users into casino PWAs appeared first on Arabian Post.

The malware, known as Ousaban or Javali, has long been associated with attacks on financial users in Brazil. Its latest campaign shows a more selective and evasive operation aimed at Windows users in the Iberian Peninsula, where the attackers use phishing documents that pretend to be corrupted files and direct victims towards a malicious web page. The campaign was identified in May 2026 and has since drawn attention because of the layered delivery method and the attempt to restrict access to people in the target countries.

The attack begins with a PDF that displays a deceptive error-style message and urges the user to press an “Update” button. The file also contains hidden JavaScript that can open the same malicious page without relying only on the visible button. The use of hex-escaped code makes the PDF harder to assess through simple inspection and allows the phishing lure to perform as both a social-engineering document and a technical trigger.

Once the victim reaches the web page, the operation becomes more selective. The site checks language, time zone and IP-related information to determine whether the visitor appears to be in Spain or Portugal. Earlier versions of the campaign also looked for signs of automated analysis, including screen resolution, browser rendering details and installed fonts. Traffic associated with VPNs was blocked by checking organisation details for terms linked to anonymisation services.

The newer version moves much of that screening to the server side. Visitors who fail the check receive a Spanish-language access-denied PDF stating that the service is not available from their country. This tactic reduces the number of visible indicators available to researchers, because security sandboxes and crawlers may receive only a harmless-looking denial message instead of the malware chain.

Victims who pass the check receive a VBS file that begins the next stage. The script contains numerous benign calls to make the file appear less suspicious, while the active code downloads an image resembling a PDF icon. The attackers use steganography by appending a ZIP archive to that image. The script extracts the archive, retrieves the Ousaban payload and drops it onto the machine, before deleting the temporary files used during the installation.

The payload is placed under a system-style folder path and establishes persistence through a registry value named “Financeiro”, Portuguese for finance, under the Windows Run key. It also creates an empty file used as an installation timestamp. Once active, Ousaban decrypts bank-related strings and watches for access to banking services. The targeted institutions include major lenders and financial brands in Spain and Portugal, covering names such as Santander, BBVA, CaixaBank, Bankinter and Caixa Geral de Depósitos.

Ousaban’s capabilities are typical of credential-focused banking malware but remain dangerous because they are deployed only when the victim is likely to be useful. The trojan can collect system information, capture screenshots, log keystrokes, alter clipboard contents, display fake messages and give attackers remote control over the machine. These functions are designed to support account takeover, payment manipulation and further fraud once the user interacts with online banking services.

The command-and-control system has also been designed to frustrate tracking. The malware carries a Pastebin link that points to configuration data containing a private IP address, but that appears to be a decoy. The active command server is reached through a hostname that changes daily. The hostname is generated using a hard-coded string and the current date, with the malware obtaining date information by accessing a Google automated-queries page. If the hostname resolves, the malware connects to the server and waits for commands.

Most traffic between Ousaban and its controller is encrypted through a custom algorithm used by Latin American banking trojans. The method introduces random values so that the same plaintext can produce different encrypted strings, complicating static analysis and signature-based detection. Similar encryption has been observed in families such as Casbaneiro, underscoring the shared techniques among malware groups that grew out of Latin America’s banking-fraud ecosystem.

The campaign reflects a wider trend in which mature regional banking trojans are being adapted for European markets. Spain has been a frequent test ground for this expansion because of language overlap, large retail banking networks and digital-banking adoption. Portugal offers a similar opportunity for Portuguese-language lures and Brazil-linked social-engineering themes.

The article Ousaban widens banking threat across Iberia appeared first on Arabian Post.

The campaign, tracked as Veil#Drop, begins with a JavaScript file disguised as a document, such as “transcript. pdf. js”. Once opened on a Windows system, the file runs through Windows Script Host and launches PowerShell with execution-policy bypasses enabled. The command then retrieves further payloads from attacker-controlled Blogspot pages, allowing the malicious traffic to blend with ordinary access to Google-owned infrastructure.

Security researchers said the framework loads PureLog Stealer through a chain of PowerShell download cradles, XOR-obfuscated code and. NET reflection, avoiding the need to write a conventional executable file to disk. The final payload is designed to harvest browser credentials, cookies, autofill data, browsing history, cryptocurrency wallet details and system information.

The use of Blogspot marks a notable escalation in the misuse of mainstream cloud and publishing platforms. By staging payloads on a familiar domain, attackers can reduce suspicion and weaken reputation-based blocking. The technique also complicates incident response because defenders may be reluctant to block an entire trusted service without disrupting legitimate users.

Veil#Drop relies heavily on native Windows tools. The initial JavaScript launcher spawns PowerShell, which retrieves and executes code in memory. Later stages reconstruct encrypted. NET assemblies at runtime and load them through reflection. The framework also includes fallback execution through Microsoft-signed utilities such as RegSvcs, InstallUtil, MSBuild, CSC, VBC and AspNet_Compiler, a tactic often described as “living off the land” because it uses legitimate binaries already present on the system.

The campaign’s social-engineering component remains central to its success. Attackers use double extensions and document-themed names to exploit the way many Windows systems hide known file extensions by default. A victim may see what appears to be a PDF, while the operating system executes a JavaScript file. The approach does not require a software vulnerability; it relies on trust, routine office behaviour and poor visibility into file types.

PureLog Stealer has become a persistent presence in credential-theft campaigns over the past year. Earlier operations used copyright complaint lures, invoice themes, purchase-order messages and malicious archives to push PureLogs variants at organisations and individuals. Other delivery chains have used encrypted payloads hidden inside image files, process hollowing and PowerShell-based loaders to evade static inspection.

The malware family is valued by criminals because stolen browser cookies and session tokens can bypass some multi-factor authentication protections. Once a session token is taken from an infected device, attackers may be able to access cloud email, business applications or cryptocurrency accounts without needing the victim’s password again. That risk is especially acute for finance teams, media organisations, government offices and small businesses that rely heavily on browser-based services.

The campaign also reflects a broader shift away from noisy malware droppers towards modular infection chains. Rather than placing a full malicious executable on the endpoint, attackers use small launchers, trusted services, encrypted blobs and memory-only execution. Each stage performs a narrow task, making detection harder and giving operators room to update infrastructure quickly if a domain or payload is blocked.

For defenders, the case highlights the limits of signature-based antivirus tools. Useful warning signs include unusual parent-child process chains such as wscript. exe launching powershell. exe, PowerShell using Invoke-RestMethod or Invoke-Expression to fetch remote content, encoded command execution, unexplained access to Blogspot URLs from endpoints, and. NET assemblies being loaded directly into memory. Monitoring trusted Microsoft utilities for abnormal execution is also becoming more important as attackers increasingly use them as fallback launch paths.

The practical response is less about blocking one platform and more about tightening execution controls. Organisations can reduce exposure by showing file extensions by default, restricting Windows Script Host where it is not required, applying PowerShell logging and constrained language mode, monitoring command-line activity, limiting outbound traffic from user endpoints, and using behavioural detection capable of flagging memory-only malware chains.

The article Blogspot used in stealth infostealer campaign appeared first on Arabian Post.

The article ClawHub breach exposes agent marketplace risk appeared first on Arabian Post.

The campaign has accelerated sharply this year, with about 39,700 infections recorded during the first quarter of 2026 alone. The scale points to an expanding malware-as-a-service operation in which attackers can rent or buy a ready-made spying tool, use Telegram as command infrastructure and avoid the cost of maintaining dedicated servers.

Millenium RAT version 4 marks a significant technical shift from earlier builds. The malware has moved from. NET to native C++, making it less dependent on installed frameworks and more difficult for basic detection systems to flag through older signatures. Its operators continue to rely on Telegram’s bot application programming interface for command and control, allowing malicious traffic to blend with legitimate messaging activity.

The trojan is designed to take extensive control of infected Windows machines. Its functions include stealing browser and system data, capturing screenshots, recording audio, logging keystrokes, downloading and running additional files, listing folders and processes, and attempting privilege escalation through standard Windows prompts. Such capabilities place personal users, small businesses and poorly monitored corporate endpoints at risk of credential theft, financial fraud and follow-on intrusion.

The malware is being sold cheaply. Subscription models linked to the tool have included an initial monthly price of about $50, lower renewal costs and a lifetime option of about $90. Earlier versions were advertised for even less, showing how criminal software is moving towards consumer-style pricing and support models. This affordability lowers the barrier for less capable attackers, enabling broader campaigns without requiring advanced coding skills.

Security analysis has linked current exploitation activity to a cluster tracked as Y2K Operators, while development and promotion have been associated with the online alias ShinyEnigma. The tool has been advertised not only in underground spaces but also through mainstream code-sharing platforms, some of which later removed related repositories. That pattern reflects a recurring problem for open developer ecosystems, where offensive tools can be presented as research or administration utilities before being adapted for abuse.

The infection routes observed in the campaign rely heavily on social engineering. Victims are lured into opening compressed archives, disguised executable files or shortcut files made to look like documents. One chain uses a file posing as a PDF, which launches PowerShell in the background, downloads a script, shows a decoy document and quietly runs the Millenium RAT payload. Other samples use names resembling system processes, browser updates, antivirus components or generic installers to reduce suspicion.

The operators have also targeted other cybercriminals by circulating trojanised versions of RAT builders, exploit kits and similar tools. This tactic infects would-be attackers who download what appears to be a working offensive utility, turning criminal forums and malware markets into distribution channels as well as customer bases. It underlines how the cybercrime economy increasingly feeds on itself.

Millenium RAT’s configuration is embedded inside the malware and protected with Base64 encoding and a custom XOR-based routine. It stores Telegram bot tokens, chat identifiers, persistence settings, keylogging options, sandbox checks and file paths used during installation. The malware can create autorun entries under the current user’s registry hive and place files inside user-writable application folders, helping it restart after a reboot.

Its use of ordinary Windows application programming interfaces gives it a further advantage. Rather than relying on exotic techniques, it performs many actions through functions that are common across legitimate software. That makes behaviour-based monitoring more important than static file matching, particularly because the malware can alter configuration data to change file hashes while preserving its core capabilities.

The campaign fits a broader shift in cybercrime. Intrusions are moving faster, malware services are becoming cheaper, and attackers are increasingly exploiting trusted platforms, cloud services and identity systems instead of depending only on bespoke criminal infrastructure. Messaging platforms, software repositories and file-sharing services remain attractive because they provide scale, credibility and resilience.

For organisations, the practical risk is not limited to the first infected machine. A RAT can serve as an entry point for credential theft, lateral movement, data theft or ransomware deployment. Stolen browser passwords, session cookies and cryptocurrency wallet data may give attackers access to email, banking, cloud dashboards and business applications even after the original malware is removed.

The article Cheap RAT spreads through Telegram channels appeared first on Arabian Post.

The flaw, tracked as CVE-2026-20245, affects Cisco Catalyst SD-WAN Controller, Catalyst SD-WAN Manager and Catalyst SD-WAN Validator, formerly known as vSmart, vManage and vBond. It allows an authenticated local attacker to execute arbitrary commands with root privileges by uploading a specially crafted file through the command-line interface. Cisco rated the vulnerability high severity, with a CVSS score of 7.8.

Google’s Mandiant researchers said exploitation was observed during an intrusion into SD-WAN infrastructure at a service provider. The attacker first gained access to the environment, then used the vulnerability to move from an administrative account to root-level control. The activity was traced to March, while Cisco’s public advisory was issued on 4 June and later updated with fixed release information.

The case adds to a growing pattern in which attackers focus on edge and network-management devices rather than conventional endpoints. Such systems often sit at privileged points in enterprise architecture and may have weaker telemetry than servers or laptops, making stealthy access harder to detect. SD-WAN managers are particularly sensitive because they control routing, policy and connectivity across distributed networks.

Investigators found that the attacker created unauthorised peering connections, used Secure Shell access, manipulated default account passwords and accessed the SD-WAN Manager web interface. Configuration details of the SD-WAN fabric were extracted. The attacker later restored account settings, an apparent attempt to avoid raising suspicion during normal administrative activity.

The vulnerability was exploited in April through a malicious CSV upload. The payload altered system files, created backups and added a root-level user account named “troot”. The attacker then used that account to gain full control. After completing the operation, the intruder deleted files, restored modified configurations and ran a validation script to check whether traces of the activity had been removed.

Cisco said exploitation requires an attacker to already hold network administrator privileges on the affected system. That access could be obtained through valid credentials or through prior exploitation of other Cisco Catalyst SD-WAN flaws, including CVE-2026-20182 and CVE-2026-20127. Both relate to authentication and peering mechanisms and have heightened scrutiny of SD-WAN management infrastructure.

The chronology has sharpened concerns among defenders because unauthorised peering activity was seen from late 2025 to January 2026, before further activity emerged in March. Researchers have not confirmed that all phases were conducted by the same actor. Cisco separately linked earlier SD-WAN exploitation to a threat group tracked as UAT-8616, which had targeted vulnerable controller infrastructure.

Cisco initially said there were no workarounds for CVE-2026-20245 and urged customers to upgrade to fixed software and verify edge-device configurations. Its updated advisory listed fixed releases, including 20.15.4.5 and 20.15.5.3, and advised administrators to review logs for signs of unauthorised access, unexpected peering connections and suspicious command execution.

The attack chain shows why credential security alone may not be sufficient. Once an attacker reaches an administrative account, privilege escalation can turn limited management access into system-level control. From there, changes to routes, policies and connected edge devices can give intruders a powerful vantage point inside corporate networks.

The affected technology is widely used by large, distributed organisations such as banks, retailers, healthcare groups, technology providers and managed service firms. SD-WAN helps route traffic between offices, data centres and cloud platforms, but the same centralised design can magnify risk when management systems are compromised.

Security teams have been advised to treat SD-WAN controllers as critical assets rather than routine network appliances. That means restricting management access, removing unnecessary internet exposure, enforcing strong administrative controls, checking certificates, reviewing peering relationships and preserving logs that may otherwise be unavailable after attacker cleanup.

The article Cisco flaw hit before public warning appeared first on Arabian Post.

The technique, described as cloud bucket hijacking, exploits the way many cloud providers use globally unique storage names to route logs, telemetry and replicated objects. If a bucket is deleted but an automated service continues to send data to that destination name, an attacker who can recreate the same name in another account or subscription may receive the continuing data stream.

The finding carries significance because cloud storage buckets are widely used as destinations for audit logs, application telemetry, backup streams, object replication and data lake pipelines. These flows are often configured once and then left to run automatically. That “set and forget” pattern can turn a deleted bucket into a hidden exfiltration channel if identity and access controls allow deletion by compromised or over-privileged accounts.

No active exploitation by a named threat actor has been identified. The concern is that the method is difficult to detect once a routing resource remains valid and the flow continues. Security teams may see no immediate failure in the logging or replication configuration, even though the destination has changed ownership.

The weakness differs from the familiar problem of public cloud buckets being exposed through poor permissions. In those cases, data is often left openly accessible. Cloud bucket hijacking instead relies on name reuse and automated routing. The victim’s cloud service may continue sending information to a bucket bearing the expected name, while the bucket itself has been re-created in an attacker’s environment.

Tests found that the concept could affect multiple services. In Google Cloud, logging sinks, Pub/Sub delivery and Storage Transfer Service were among the areas assessed. In AWS, S3 replication and Amazon Data Firehose showed related exposure where data streams target S3 buckets. Azure presented a narrower version because storage account names are not immediately reusable across tenants after deletion, but cross-subscription abuse remained possible under certain conditions.

The issue highlights a broader architectural risk in cloud computing: identity is sometimes tied to a resource name rather than to a permanent owner. Globally unique bucket names simplify routing and reduce naming conflicts, but they also create a shared namespace. Once a resource is deleted, the name may eventually become available again, allowing another account to claim it unless provider-level safeguards or account-scoped naming are applied.

The implications are sharper because cloud infrastructure spending is accelerating as companies expand artificial intelligence, analytics and digital operations. The largest providers together control the majority of enterprise cloud infrastructure expenditure, making cross-cloud weaknesses especially important for multinational companies that run workloads across several platforms.

The attack path would still require meaningful access. A threat actor would generally need the ability to delete a bucket or storage account, or exploit an abandoned routing configuration left behind by an organisation. That makes excessive permissions a central risk. Broad storage administrator roles, service accounts with deletion rights and poorly governed DevOps permissions can raise exposure.

Defensive steps focus on reducing deletion rights and ensuring data cannot leave trusted boundaries. Cloud teams are being urged to restrict bucket and storage account deletion privileges to a small group of administrators, remove those rights from routine service accounts, and require stronger approval workflows before deletion of high-value storage.

Monitoring is also critical. Organisations should treat deletion of sensitive storage buckets as a high-severity event, especially where the bucket is linked to logs, telemetry or replication. Alerts should be tied to business context, because large cloud estates can generate many storage events. Data security posture management tools and cloud-native audit monitoring can help distinguish ordinary housekeeping from risky deletion of critical destinations.

Provider-level controls also matter. Account-scoped or region-scoped naming reduces the risk that another account can reclaim a deleted bucket name. Data perimeter policies can block workloads from writing to storage outside the trusted organisation. Google Cloud has adjusted how some router resources interact with target storage resources, while Microsoft has directed customers towards guidance on dangling DNS and takeover risks. AWS offers mechanisms that can scope bucket naming and restrict cross-account writes when configured properly.

The finding is likely to strengthen scrutiny of cloud governance at a time when enterprises are moving more audit, security and application data into automated pipelines. For regulated sectors such as finance, healthcare, energy and government services, the loss of audit logs or telemetry may undermine both incident response and compliance reporting.

The article Cloud bucket flaw exposes silent data theft risk appeared first on Arabian Post.

The assessment found that the incident fell below the threshold for a formal Category 1 national cyber event, which requires losses of at least £10m or an impact on more than 0.01 per cent of UK organisations. Even so, the case has become an important test of how data theft differs from outages that halt operations, with costs driven more by response, recovery, legal review and risk management than by prolonged business interruption.

Canvas, the learning management system owned by US-based Instructure, is widely used by universities, colleges and specialist institutions for coursework, assessments, grades and communication between students and academic staff. The breach was detected on April 29, when unauthorised activity was identified inside Canvas. A second intrusion on May 7 allowed the same threat actor to alter pages seen by some users after login, prompting the company to place the platform into maintenance mode while access was contained and additional safeguards were applied.

The attackers were linked to ShinyHunters, a cybercriminal group known for large-scale data theft and extortion campaigns. Data taken from the platform included usernames, email addresses, course and enrolment information, student identification numbers and, in some cases, messages exchanged through the system. Instructure has said it found no evidence that passwords, dates of birth, government identifiers or financial information were compromised.

The CMC review concluded that disruption in the UK was generally limited in duration and scope because universities retained some ability to continue teaching and administration through alternative methods. Human-led delivery, email, virtual meeting tools and local contingency arrangements helped reduce the operational impact. That resilience, the centre noted, may not exist in more automated sectors where a comparable platform failure could interrupt revenue-generating services more directly.

The incident has nevertheless highlighted the growing exposure of education providers to third-party software risks. Higher education depends heavily on cloud platforms, digital identity systems, student records, payment tools, research repositories and software-as-a-service applications. A failure in one widely used platform can therefore affect multiple institutions at once, even where local networks have not been breached.

Instructure has said the attacker used one of its Free-for-Teacher accounts in both phases of the incident. The company has discontinued that product, remediated the vulnerabilities and privilege escalation paths used in the attack, and advised customers to continue normal monitoring of Canvas environments, integrations and administrative activity. Its forensic review found no evidence of current attacker access to the platform or lateral movement into other Instructure products.

The absence of confirmed lateral movement into university systems has reduced immediate concern about deeper compromise. But stolen data remains useful to criminals. Names, course details, student identifiers and internal messages can support phishing, impersonation and social engineering campaigns aimed at students, academics and administrators. Attackers can use education-specific context to make fraudulent emails appear more credible, particularly during exam, enrolment and fee-payment periods.

The CMC’s technical recommendations place particular emphasis on risk-based architecture. Institutions have been urged to identify mission-critical services, separate application and data layers where possible, apply multifactor authentication uniformly, control third-party privileges and rehearse breach scenarios through business continuity exercises. The centre also called for stronger oversight of offshore providers that may not be subject to UK law in the same way as domestic suppliers.

The warning comes as cyber incidents across education remain above the level seen in many other sectors. The 2025/26 cyber security survey for educational institutions found that 98 per cent of higher education institutions had identified breaches or attacks over the previous 12 months. Further and higher education providers also reported more frequent incidents than schools and businesses, with 27 per cent experiencing a breach or attack at least weekly.

Phishing remained the dominant threat, reported by 96 per cent of further and higher education institutions that had identified an incident. Impersonation, malware and compromised accounts were also significant risks. Nearly half of further and higher education providers that identified a breach suffered a negative system outcome, including compromised accounts being used for illicit purposes, online services slowing or going offline, and loss of access to files or networks.

Sector preparedness has improved in some areas. Every higher education institution covered by the survey had a senior leader responsible for cyber security, and 84 per cent updated governors or senior management at least quarterly. Cyber insurance uptake has also increased, with 61 per cent of higher education institutions holding a dedicated cyber security policy, up from 34 per cent in the previous cycle.

The weaknesses remain substantial. Nearly half of higher education institutions said they held personal data on employees or students that was not protected through anonymisation or encryption. Fewer institutions were testing staff awareness than before, even as threat intelligence use rose sharply. For universities already balancing budget pressure, research security obligations and student data duties, the Canvas breach has turned supplier risk into a board-level governance issue rather than a narrow IT problem.

The article Canvas breach sharpens UK campus cyber warning appeared first on Arabian Post.

The malware, tracked as macOS. Gaslight, is written in Rust and contains a 3.5 KB prompt-injection payload made up of 38 fabricated “system” messages. The messages are not aimed at Apple’s operating system or at a conventional sandbox. They appear built to manipulate large language model-based triage tools that analysts increasingly use to summarise code, inspect binaries and accelerate reverse engineering.

The case marks a shift in attacker behaviour. Malware authors have long used packing, obfuscation, encrypted strings and anti-debugging checks to slow down human investigators and automated scanners. Gaslight adds another layer by treating the analyst’s AI assistant as part of the target environment. Its embedded text mimics internal error messages and tool instructions, including claims about token expiry, disk exhaustion, memory failure and unsafe analysis conditions, apparently attempting to make an AI agent stop, truncate or refuse its work.

The sample was uploaded to VirusTotal on May 22 and came to wider attention after an Apple XProtect update in early June flagged it through a hash-based rule. The binary was ad hoc signed and used the identifier “endpoint-macos-aarch64-5555494492fc075f441637fb9d894913dde3a2ea”. Static detection remained limited at the time of analysis, underlining the continuing difficulty of catching bespoke macOS implants before wider exposure.

Gaslight’s capabilities go beyond deception of AI systems. The implant uses Telegram’s Bot API as a command-and-control channel, polling for operator instructions and returning stolen data through Telegram’s file-upload mechanism. Its traffic is hardened with AES-GCM encryption and certificate-pinned TLS, a combination that can frustrate inspection by enterprise network tools that rely on proxy certificates.

The malware also includes an operational security feature that redacts the Telegram bot token from its own runtime output. That limits the ability of defenders who capture logs or crash artefacts to recover a live credential and use it to inspect operator activity. Telegram-based command infrastructure is common across criminal and state-linked malware, but deliberate self-redaction within runtime output adds another obstacle for incident responders.

Once activated, the implant can provide an interactive shell, execute commands, kill processes, upload files and stop itself. It also creates a macOS power-management assertion to prevent the system from sleeping, allowing longer command-and-control sessions and data collection during periods of user inactivity. Persistence is handled through a LaunchAgent using the label “com. apple. system. services. activity”, a name chosen to resemble Apple system services.

A bundled Python-based collection module expands the threat. The decoded script is designed to harvest browser data from Chrome, Brave, Firefox and Safari; terminal command histories; installed application lists; process snapshots; system hardware and software profiles; and a raw copy of the macOS login keychain database. Collected artefacts are archived and uploaded back to the operator. A separate installer can fetch a standalone CPython 3.10.18 build at runtime, allowing the Rust implant to stage a richer data-theft environment only when required.

The attribution places Gaslight within a broader pattern of North Korea-linked macOS activity aimed at cryptocurrency, finance, blockchain and technology targets. Operators associated with these campaigns have used fake job interviews, bogus video-conferencing updates, developer tools and social engineering to persuade victims to run malicious files manually. Such tactics allow attackers to bypass some platform protections by shifting execution into a user-approved context.

The timing is significant because AI is being embedded into security operations at speed. Malware analysts, endpoint vendors and corporate security teams are using large language models to summarise suspicious files, generate detection logic, parse logs and explain unfamiliar code. Those tools can improve speed, but they also ingest untrusted text from exactly the kind of files adversaries control.

Prompt injection has already moved from academic concern to operational risk. Attackers have hidden instructions in web pages, documents, metadata and code comments to influence AI agents that summarise, moderate or process external content. Gaslight shows the same idea migrating into malware analysis, where a binary can carry text meant not for the machine it infects, but for the model asked to examine it.

The defensive lesson is narrow but important. AI-assisted triage systems cannot treat sample contents as trusted instructions. Malware strings, comments, embedded Markdown and decoded payloads need to be isolated as evidence, not placed in a model context where they can override the task. Security teams using AI in reverse engineering will need stronger separation between system prompts and hostile artefacts, prompt-injection filtering, audit trails for model decisions and human review of refusals or unexplained analysis failures.

Apple’s built-in protections and vendor detections can still reduce exposure when systems are patched, but Gaslight highlights the limits of relying on traditional indicators alone. The sample combines established macOS tradecraft with an attack surface created by modern security practice itself. For high-value organisations, the risk is no longer only that AI misses malware. It is that malware may try to instruct AI not to look.

The article Gaslight malware exposes AI triage blind spot appeared first on Arabian Post.

NCC Group has warned that threat actors tied to governments are using ransomware branding, extortion notes, victim leak sites and negotiation channels not only to increase pressure on targets but also to complicate attribution. Its latest threat intelligence assessment highlights a campaign associated with MuddyWater in which activity presented as a Chaos ransomware incident showed signs of a targeted intelligence operation rather than a conventional profit-driven attack.

The warning comes as ransomware volumes remain elevated across the global threat landscape. NCC Group recorded 749 ransomware attacks worldwide in May 2026, with industrial organisations accounting for 29 per cent of known incidents. Qilin remained the most active ransomware operation during the month, responsible for 15 per cent of tracked activity, while The Gentlemen ranked second for another consecutive month, underscoring the rapid churn of ransomware operators and affiliate ecosystems.

MuddyWater, also tracked as Seedworm, Static Kitten, TEMP. Zagros and Mango Sandstorm, has been active since at least 2017 and is widely assessed to operate as part of Iran’s intelligence apparatus. Its targeting has included government bodies, telecommunications providers, local authorities, financial institutions, defence entities, oil and gas organisations and critical infrastructure across the Middle East, Europe, Asia, Africa and North America. The UAE and Saudi Arabia have appeared among the group’s established areas of interest.

The campaign highlighted by threat researchers began as a case that appeared to fit the pattern of a Chaos ransomware intrusion. The attackers used social engineering, remote access tools, credential theft and data exfiltration before introducing ransomware-style elements. The victim was pushed into channels associated with extortion, creating the impression of a financially motivated attack. Forensic details, however, pointed towards espionage objectives, including access maintenance, intelligence collection and operational tradecraft consistent with MuddyWater.

A key feature of the operation was the use of commercially available and legitimate remote administration software to establish access. Attackers posed as technical support personnel and persuaded a target to install remote access tooling, allowing them to deploy additional malware, harvest credentials, alter multi-factor authentication settings and move deeper into the network. This method reduces the need for bespoke malware at the initial stage and allows intruders to blend into ordinary enterprise activity.

The deployment of ransomware branding after the espionage phase marks a notable development. Traditional ransomware actors typically prioritise encryption, public pressure and payment. In the MuddyWater-linked case, the sequence of activity suggested that the extortion layer may have functioned as a smokescreen after sensitive information had already been collected. That approach can mislead investigators, delay diplomatic attribution and force victims to treat the incident as a criminal extortion case while intelligence loss remains the more serious consequence.

The tactic is not entirely new for MuddyWater. The group has previously been associated with disruptive activity disguised as ransomware, including operations that used false criminal personas to obscure state interests. What has changed is the sophistication and credibility of the cover. Ransomware-as-a-service branding, leak-site exposure and negotiation infrastructure now provide ready-made camouflage for state-backed operators seeking plausible deniability.

MuddyWater’s broader tradecraft has also evolved. Security researchers tracking its operations have identified tailored phishing lures, hijacked trusted accounts, macro-enabled documents, custom backdoors, Rust-based implants, use of Telegram for command and control, and infrastructure designed to support large-scale email delivery. Its targets have included diplomatic, maritime, aviation, energy, finance and technology entities, suggesting a focus on economic and strategic intelligence rather than random criminal gain.

The convergence between cybercrime and state activity presents a practical problem for companies and governments. Incident responders can no longer assume that a ransom note indicates a financially motivated attacker. A ransomware label may now be part of a deception strategy, especially where attackers show unusual interest in internal communications, credentials, network persistence or data linked to strategic sectors.

The risk is particularly acute for industrial and critical infrastructure operators, which remain heavily targeted by ransomware groups and are also attractive intelligence targets. Energy, ports, telecommunications, aerospace, financial services and government suppliers face overlapping pressure from criminal gangs, state-backed espionage teams and hybrid actors that move between the two worlds.

The use of legitimate commercial tools adds another complication. Remote monitoring and management platforms, cloud services and credential utilities are common inside corporate networks, making malicious activity harder to distinguish from routine administration. Attackers benefit from this ambiguity, especially when they combine social engineering with compromised accounts that appear trusted to email filters and recipients.

The latest activity also comes against a backdrop of heightened geopolitical tension, where cyber operations often accompany diplomatic and military friction. Iran-linked groups have shown repeated interest in entities connected to defence, aviation, maritime logistics, energy supply and regional policymaking. Their operations are often designed to gather intelligence, prepare access or apply pressure while avoiding a clear threshold for overt retaliation.

The article MuddyWater masks espionage behind ransomware playbook appeared first on Arabian Post.

The operation relies on a Browser-in-the-Browser, or BitB, technique that places a convincing imitation of a browser window over a legitimate-looking webpage. Instead of depending on an automatic exploit, the attackers create the impression that a document has failed to load or that essential software is out of date, then instruct the user to download and run an installer carrying malware.

The campaign marks a further shift in web-based social engineering, where attackers abuse trust in familiar interfaces rather than relying only on suspicious attachments or obvious phishing pages. The fake windows reproduce browser chrome, software prompts and document-viewing errors closely enough to make the page appear routine to hurried users.

The lure typically begins when a victim lands on a compromised or attacker-controlled site. A staged page presents what appears to be a stalled file preview, a browser notification or a software update message. Behind the visible layer, concealed iframes and scripts manage the deception, route the user through the attack flow and hide parts of the infrastructure from automated scanning tools.

The key point in the chain is human approval. The malware does not need to break directly through the browser sandbox if the victim can be persuaded to fetch an executable and launch it. That allows the campaign to bypass some protections tuned to detect silent drive-by downloads, while leaving defenders to identify the installer, command-and-control traffic or post-compromise behaviour after execution.

BitB attacks are not new, but their use has widened from credential theft into broader malware delivery. Earlier campaigns commonly simulated single sign-on pop-ups for Google, Microsoft, Facebook, Steam or corporate identity portals. The latest pattern adapts the same visual deception for “fix”, “update” or “open document” scenarios, making it closer to ClickFix-style attacks that have spread through phishing emails, malicious ads and compromised websites.

The technique works because users have been trained for years to respond to software prompts, browser warnings and document-rendering errors. A fake modal window can display a plausible address bar, padlock icon, progress wheel and button layout. Unlike a real browser window, it remains trapped inside the page. It cannot be dragged outside the browser viewport, maximised like a separate application window or inspected through normal browser controls.

Anti-analysis features add another layer of difficulty for defenders. Campaign pages can check whether they are being opened from a virtual machine, sandbox, automated crawler or research environment. They may inspect screen size, mouse movement, language settings, browser type, timing patterns and developer-tool signals before showing the full lure. If the environment looks artificial, the page can display benign content or redirect away from the payload.

Concealed iframes also complicate detection. Legitimate websites use iframes for payments, embedded media, analytics and authentication flows, so the mere presence of a frame is not proof of compromise. Attackers exploit that ambiguity by hiding content at small dimensions, layering transparent elements or loading scripts that activate only after user interaction.

The campaign fits a wider trend in which browsers have become a primary enterprise attack surface. Work applications, identity portals, customer platforms and collaboration tools now run heavily through browsers, giving attackers a rich environment for social engineering. Stolen credentials, session cookies and malicious installers can all begin with a web page that appears to be part of a normal workflow.

For businesses, the risk is not limited to one malware family. A manually installed payload can be used as a loader for credential theft, remote access, data exfiltration or ransomware preparation. Once running, it may harvest browser-stored secrets, enumerate network resources, disable security tools or fetch additional modules from remote servers.

The article Fake browser windows drive malware downloads appeared first on Arabian Post.

The Pune-based two- and three-wheeler maker said the incident took place on 23 June at around 8am IST. Technical teams, senior management and external cybersecurity specialists responded after the breach was detected, triggering precautionary protocols to contain the attack and limit operational impact. The company said the response measures had been successful based on information available at the time of its stock exchange filing.

The disclosure was made under corporate governance norms and the incident has been reported to the Indian Computer Emergency Response Team, the national cyber incident response agency, in line with the Information Technology Act, 2000. Bajaj Auto did not specify the ransomware strain, identify the attackers, disclose whether any ransom demand had been made, or state whether data had been stolen.

The absence of detail on possible data exposure leaves investors and customers waiting for further clarity. Ransomware attacks often begin with unauthorised access to internal systems before attackers encrypt files, exfiltrate data, or threaten public disclosure. Companies sometimes describe containment as successful while forensic teams continue to assess whether information was copied before systems were isolated.

Bajaj Auto’s shares fell after the disclosure, dropping around 2 per cent in morning trade on 24 June and becoming one of the weaker performers on the Nifty 50. The timing drew attention because 24 June was also the record date for the company’s ₹5,632 crore share buyback. The board had approved a tender offer to repurchase up to 46.94 lakh equity shares at ₹12,000 apiece, representing 1.68 per cent of paid-up equity capital.

The market reaction came despite Bajaj Auto’s strong March-quarter performance. Standalone net profit for the quarter rose 34 per cent year-on-year to ₹2,746.13 crore, while revenue from operations increased 31.8 per cent to ₹16,005.7 crore. Earnings before interest, tax, depreciation and amortisation rose 35.6 per cent to ₹3,322.7 crore, with the operating margin expanding to 20.8 per cent.

The cyberattack places fresh focus on technology resilience inside manufacturing groups, particularly those with large dealer networks, vendor ecosystems, export operations and connected enterprise systems. Bajaj Auto operates in a sector where digital platforms now manage production planning, supplier coordination, sales channels, warranty systems and finance-linked customer services. Even limited disruption can affect logistics, invoicing, procurement and customer-facing applications if core systems are isolated during containment.

The company’s technology subsidiary is central to that concern. Bajaj Auto Technology Limited supports digital and engineering capabilities within the group, making its inclusion in the disclosure significant. A compromise involving both parent and subsidiary systems suggests that investigators will need to examine whether the breach moved laterally across shared infrastructure or through linked applications.

The incident also comes amid a sharp escalation in cyber threats against industrial and technology-linked businesses. Industrial organisations have become high-value targets because downtime can create pressure to settle quickly. Threat groups have shifted from simple encryption attacks to double-extortion tactics, where stolen data is used to force payment even when a company can restore systems from backups.

Manufacturers face a distinct challenge because they must protect both information technology and operational technology. Legacy equipment, third-party remote access, production software and supplier portals often create entry points that are harder to monitor than standard corporate networks. Cybersecurity teams therefore increasingly treat incident response, backup segregation and supplier access controls as board-level issues rather than routine IT functions.

The Bajaj disclosure follows other cyber incidents involving major business groups and suppliers, underscoring how attackers are targeting companies embedded in global supply chains. The risk is no longer confined to banks, software firms or consumer platforms. Auto, electronics, logistics, energy and industrial equipment companies have become frequent targets because their systems connect commercial data, intellectual property and time-sensitive operations.

The article Bajaj contains ransomware breach after systems hit appeared first on Arabian Post.

The finding has sharpened concerns over trust signals in the fast-growing AI agent ecosystem, where plugins and skills can run commands, connect to external services, modify files and act on a user’s behalf. The issue, identified by Manifold Security during a catalogue review and reported to ClawHub on 17 June, centred on inconsistent enforcement of a rule that was meant to stop publishers from using organisational scopes they did not control.

ClawHub’s documentation says a plugin scope must match the selected publishing owner. That control is designed to prevent a package from claiming an organisation’s namespace without permission. Yet unaffiliated accounts were able to place plugins under names that appeared to belong to OpenClaw or ClawHub itself, giving third-party code the look of a first-party integration.

The registry later unlisted the misleading plugins and introduced a formal process for disputing organisational scopes and namespaces claimed by unauthorised entities. The response appears to have reduced immediate exposure, but the episode has underlined how easily provenance cues can be abused when marketplace governance lags behind adoption.

ClawHub is the public registry for OpenClaw skills and plugins. It allows users to search, install and update agent extensions, including Claude-compatible plugin bundles used with AI coding tools such as Claude Code, Cursor and Codex. The registry indexes more than 1,500 plugins, with hundreds using @owner-style scopes similar to those in established software package ecosystems.

Those scopes are not cosmetic. Developers often treat an @organisation/package format as a sign that the code has been published or approved by the named organisation. A plugin called under @openclaw/ can therefore look more trustworthy than an unknown standalone package, particularly when genuine OpenClaw integrations also use the same namespace.

The 23 flagged plugins were spread across 15 distinct accounts. Some were marked clean while others were described as suspicious, but the core issue was broader than whether specific packages contained malware. The risk lay in the registry allowing code-executing extensions to inherit institutional credibility without a verified relationship to the institution.

Several of the plugins had capabilities that could matter in an enterprise environment, including access to external APIs, payment-related workflows, host-level git commands and agent configuration export. In an AI agent setting, such permissions can carry higher impact than a conventional browser add-on or utility script because agents often operate inside development environments, repositories, terminals and connected business services.

The case is part of a widening pattern of security pressure around agent extension markets. Earlier this year, researchers showed that ClawHub ranking signals could be manipulated, allowing a malicious skill to climb to a prominent position and attract executions. Another investigation described a fake Google-themed skill that used setup instructions to steer users into running malware outside the registry package itself.

These incidents point to a common weakness: AI agent tools combine software distribution, automation and user trust in a way that gives attackers several routes to abuse. A malicious package does not always need complex obfuscation. It can exploit naming, ranking, installation prompts or the agent’s own instructions to gain credibility.

The ClawHub scope-squatting issue also illustrates the difference between written policy and technical enforcement. Publishing guidance may tell users that namespace controls exist, but users are exposed if the registry does not apply those controls consistently across every publishing path and historical entry. Mature ecosystems such as npm have spent years hardening organisation membership, package ownership and transfer processes because namespace trust is a recurring attack surface.

Security teams assessing agent tools are now being urged to treat plugin provenance as a control point rather than a convenience feature. That means verifying publisher ownership, reviewing source repositories and commit metadata, restricting agent permissions, monitoring runtime behaviour and blocking plugins from performing actions outside their expected purpose.

The article ClawHub namespace lapse exposes agent plugin risk appeared first on Arabian Post.

The malware, named AryStinger by threat researchers, has been observed targeting routers built around RTL819X-series chipsets, a generation widely used in consumer and small-office networking equipment from roughly 2012 to 2015. The affected devices are led by D-Link DIR-850L and DIR-818LW models, both of which have passed their service life and no longer receive firmware fixes.

The campaign marks a shift from the more familiar use of infected routers for crude distributed denial-of-service attacks. AryStinger appears designed as reconnaissance infrastructure, allowing operators to split large scanning jobs across thousands of compromised devices. Each infected router can act as an “executor”, probing domains, testing services, forwarding traffic and helping attackers disguise their true location before deeper intrusions are attempted.

The known infection count covers RTL819X-class routers only. A second version of the malware, written in Go and aimed at network-attached storage devices, has also been identified, but its scale remains unclear. That leaves open the possibility that the real footprint of the operation is larger than the router count now visible through exposed backdoor behaviour.

DIR-850L devices account for the largest share of identified infections, followed by DIR-818LW units. Other affected models include DIR-816L, DIR-818L, DWR-118 and DIR-817LW. Geographically, the detected router infections are concentrated in South Korea and China, with smaller clusters in Sweden, Malaysia and Singapore. The distribution reflects where unsupported devices remain online rather than where the operators are based.

AryStinger gains persistence by deploying Dropbear, a lightweight SSH server, on compromised routers. It then opens access through firewall changes, allowing the attacker to maintain remote login capability. The malware communicates with command-and-control servers using HTTP or HTTPS, with traffic encoded through Protobuf and protected by simple XOR encryption. Once enrolled, each device receives an identifier and waits for tasks.

Those tasks can include IP scanning, DNS scanning, HTTP availability checks, tunnel forwarding, command execution and payload delivery. The Go-based version is broader, adding tools used for service discovery, subdomain enumeration and web probing. The router-focused version is leaner, reflecting the limited processing power of older embedded hardware.

The malware has been seen exploiting long-known vulnerabilities, including CVE-2013-3307 and CVE-2016-5681, as well as CVE-2025-11837 in the NAS-focused variant. The reliance on old flaws highlights the enduring risk posed by abandoned hardware that remains connected long after official support ends. Some of the targeted products have been outside normal firmware maintenance for years.

D-Link’s lifecycle notices for many of the affected DIR-series devices state that end-of-life and end-of-service products no longer receive technical support, firmware updates or security remediation. Users are advised to retire and replace them, rather than expect patches for newly disclosed exploitation paths. That position leaves households and small businesses exposed if they continue using older units at the edge of their networks.

The threat is not limited to the owner of the infected router. A compromised device can become a staging point for attacks against third parties, making traffic appear to originate from a residential or small-office connection. It can also be used to inspect local network activity, alter DNS settings, redirect users to phishing or malware sites, and support lateral movement against other devices behind the same gateway.

The campaign also shows why attackers value routers as durable footholds. They are always on, often poorly monitored and rarely replaced unless they fail. Many users never log into router administration panels after installation, leaving default settings, exposed services and old firmware in place for years. Security tools installed on computers and phones may not detect malicious code running on the gateway itself.

AryStinger’s hardcoded communication key contains a “2024” string, but there is no confirmed evidence that the campaign began that year. What is clearer is that the operators have maintained and updated multiple malware builds, including dozens of router samples and more than 20 Go-based variants observed since April.

The article Legacy routers fuel AryStinger scanning network appeared first on Arabian Post.

The exploit, named usbliter8, targets SecureROM, the immutable code that runs before the operating system loads. Because that code is burned into the chip during manufacturing, the underlying weakness cannot be removed through an iOS, iPadOS or watchOS update. The disclosure has sharpened attention on the long-term security limits of ageing mobile hardware, particularly devices that remain widely used in corporate fleets, second-hand markets and high-risk personal environments.

The affected platforms include Apple’s A12 and A13 systems-on-chip, used in devices such as the iPhone XS, iPhone XR, iPhone 11 line and several iPad models, as well as related S4 and S5 chips used in Apple Watch Series 4, Apple Watch Series 5, the first-generation Apple Watch SE and HomePod mini. A12X and A12Z variants may be technically close to the vulnerable class, though public exploit support has not been established in the same way.

The attack is not a remote compromise. It requires physical possession of the device, access to Device Firmware Update mode and specialised USB equipment, with researchers demonstrating the technique using a microcontroller-based setup. That limits the threat for ordinary users facing typical online attacks, but it raises concern for stolen, seized or targeted devices where an attacker can handle the hardware for a sustained period.

At the centre of the issue is a weakness in the way the USB controller handles memory during DFU operations. The exploit chain combines a hardware flaw in the Synopsys DesignWare USB 2 controller with a firmware configuration weakness linked to Apple’s Data Address Resolution Table, or DART, a component used to manage direct memory access. On A12 and A13 SecureROMs, the DART configuration allowed USB-driven DMA behaviour to overwrite protected SRAM areas and interfere with the application processor boot chain.

The distinction with older and newer Apple chips is significant. A11-era devices are not affected in the same manner because the USB driver restores DMA addresses after packets, limiting the relevant overwrite path. A14 and later platforms appear to configure DART more securely, making the same practical exploitation route far harder. That leaves A12 and A13 generations exposed to a class of attack that sits beneath the software layer Apple can normally update.

Once successful, the exploit can achieve code execution inside SecureROM and modify DFU behaviour. Researchers said the technique can inject custom USB handlers, bypass parts of the normal trust chain and boot unsigned iBoot images. On A12 and S4/S5 hardware, the path involved overwriting control-flow data near the USB DMA buffer. On A13, where Pointer Authentication Codes complicate direct stack corruption, the attack required a more complex sequence involving heap manipulation and interrupt-handling structures.

The finding extends the lineage of public Apple BootROM research beyond checkm8, the widely known exploit affecting devices up to A11. Checkm8 reshaped the jailbreak and forensic-access landscape because it operated before the operating system and could not be fully patched on affected hardware. Usbliter8 does not immediately create the same broad consumer risk, but it shows that later SecureROM generations remain vulnerable to deeply technical attacks when hardware behaviour and early-boot configuration align.

Apple was notified before publication, and the disclosure indicates engagement with the company’s product security team. No broad emergency patch is expected because the vulnerable code is not writable after manufacture. Software updates may still reduce some downstream abuse or harden later stages of the boot process, but they cannot erase the SecureROM condition itself.

The practical mitigation is therefore device management rather than a conventional patch. Users handling sensitive information are being urged to avoid leaving affected devices unattended, disable unnecessary physical access, keep passcodes strong and consider moving to A14-or-newer hardware where the disclosed exploit path is not known to apply. Organisations with high-risk staff may need to reassess older iPhone and Apple Watch deployments, especially in roles involving confidential communications, field reporting, legal work, finance or political activity.

The article Apple chip flaw exposes older devices to boot attacks appeared first on Arabian Post.

The campaign highlights a shift in botnet use from crude denial-of-service activity towards stealthier pre-intrusion work, where hijacked routers and network-attached storage appliances act as relay points between attackers and intended targets. Security analysts say the malware helps operators conceal their true location, distribute scanning tasks across many infected nodes and extend their reach inside poorly defended networks.

The botnet is built around two branches. A C-based version targets legacy routers using long-known vulnerabilities, while a more capable Go-based “Standard” branch has been observed on NAS devices. The router-focused variant has been linked to devices built around RTL819X-series chips, a hardware generation widely used between 2012 and 2015, leaving many units outside normal support cycles and unlikely to receive fresh security patches.

The affected devices include older D-Link models such as DIR-850L and DIR-818LW, along with other routers exposed to vulnerabilities including CVE-2013-3307 and CVE-2016-5681. A NAS-targeting sample has also been associated with CVE-2025-11837. The age of some flaws underlines the persistence of security debt in home and small-office networking equipment, where devices can remain connected for years after vendor support ends.

Telemetry examined by threat researchers indicates the infection base is concentrated in East and Southeast Asia, with South Korea accounting for nearly half of observed infections and China for close to one-third. Smaller shares have been identified in Sweden, Malaysia and Singapore. The geographic pattern does not necessarily show attacker origin, but it does point to clusters of exposed equipment that can be repurposed as proxy infrastructure.

AryStinger’s infected machines are referred to as “executors”, reflecting their role in carrying out instructions issued by command-and-control servers. Once active, a node can perform internal and external scanning, identify services, execute system commands, forward traffic and assist in tunnelling. The botnet can split large scanning jobs into smaller units and distribute them among compromised devices, allowing attackers to gather information at scale while reducing the visibility of any single node.

The Go-based NAS branch appears more advanced. It includes capabilities for IP and DNS scanning, command execution and payload handling in Go, Java and Python. It also integrates open-source reconnaissance and penetration-testing utilities, a pattern that has become common in intrusion campaigns because attackers can blend legitimate tools with malicious workflows and reduce the need for custom malware at every stage.

The most serious risk lies in what AryStinger enables before a visible breach occurs. By mapping exposed services, probing intranets and relaying traffic through trusted-looking residential or small-business devices, attackers can prepare later operations while making attribution and blocking more difficult. Compromised routers also sit at a sensitive position in the network path, raising the risk of DNS tampering, browsing hijacking and silent monitoring of inbound and outbound traffic.

The campaign fits a broader trend in which routers, firewalls, cameras and NAS systems have become attractive assets for both criminal operators and state-linked groups. Such devices often run lightweight Linux-based systems, face the public internet, receive less monitoring than servers or laptops and are protected by weak passwords or outdated firmware. Once compromised, they can serve as proxy nodes, staging points, data-transfer relays or launchpads for additional intrusion activity.

Botnets built from edge devices have drawn growing attention since several operations showed how residential and small-office equipment can be used to mask espionage, credential theft and scanning activity. The value of such infrastructure lies not only in scale, but in deniability: traffic routed through a consumer router or small business gateway can appear less suspicious than traffic from a known hosting provider or rented virtual server.

Mitigation is difficult where devices are obsolete. Firmware updates remain the first defence where vendors still provide them, but end-of-life equipment often requires replacement rather than patching. Administrators and users are being urged to disable remote management, change default credentials, restrict exposed services, monitor unusual DNS or outbound connections and remove unsupported routers from production networks.

For enterprises, the discovery reinforces the need to treat branch routers, NAS appliances and unmanaged edge devices as part of the attack surface rather than background infrastructure. Asset inventories, network segmentation and anomaly detection can help identify compromised devices before they become footholds for deeper intrusion.

AryStinger’s scale is modest compared with the largest IoT botnets, but its design makes it significant. Its emphasis on scanning, relay and tunnelling shows how attackers are using neglected hardware not merely to create noise, but to build quieter infrastructure for the early stages of cyber operations.

The article AryStinger turns old routers into stealth proxies appeared first on Arabian Post.

The fix, released as Beats Firmware Update 1B211 on June 16, addresses CVE-2025-20701, a high-severity vulnerability tied to Bluetooth audio code used in the earbuds. The flaw affected Beats Studio Buds, a 2021 wireless earbud model sold under Apple’s Beats brand, and centred on how a Bluetooth audio device could be paired without the user’s consent under certain conditions.

The vulnerability did not require physical possession of the earbuds. An attacker would need to be within Bluetooth range and the device would need to be in a state where it was not yet paired and actively seeking pairing requests. That narrowed the window for exploitation, but the potential impact was significant because the microphone could be accessed without the user authorising the connection.

Apple said the issue involved open-source code and that Apple software was among the affected projects. The CVE entry was assigned by a third party. The vulnerability has been credited to Dennis Heinze and Frieder Steinmetz of ERNW GmbH, a Germany-based security consultancy that has examined weaknesses in Bluetooth audio chipsets and headphone firmware.

The flaw is linked to the Airoha Bluetooth audio software development kit, which is used in audio chips found in a range of wireless earbuds and headphones. Security researchers have warned that weaknesses in such components can spread across multiple consumer products because manufacturers often rely on shared chipset platforms, firmware modules and vendor-supplied software stacks.

CVE-2025-20701 has been described as an incorrect authorisation weakness that could permit unauthorised pairing of a Bluetooth audio device. In practical terms, the vulnerability sits at the point where convenience features, such as rapid or automatic pairing, intersect with authentication controls. If a device accepts a connection request without properly verifying the other side, an attacker can gain a foothold that should not be available.

The Beats update is being delivered automatically when the earbuds are paired with, and within Bluetooth range of, an iPhone, iPad or Mac. Users can check the installed firmware version through Bluetooth settings by selecting the information button next to the connected Beats Studio Buds. Owners using Android devices can update through the Beats app, provided the earbuds are paired and connected.

The episode underlines a wider security problem facing connected accessories. Earbuds, smartwatches, trackers and other peripherals are no longer passive add-ons. They contain microphones, radios, processors, memory and firmware that interact closely with phones and computers. A weakness in an accessory can therefore become a privacy risk even when the main handset or laptop remains fully patched.

Bluetooth’s short range can create a false sense of safety. Attacks usually require proximity, but the environments in which wireless earbuds are used — offices, airports, cafés, trains, conferences and classrooms — often place potential attackers close to targets. A flaw that can be triggered without user interaction is especially concerning because the victim may receive no obvious warning that a connection attempt has occurred.

Apple’s decision to publish a security note for a Beats firmware update also reflects a shift in how major technology companies handle accessory-level vulnerabilities. Firmware patches for headphones historically attracted less attention than updates for phones, laptops or browsers. That distinction is becoming harder to justify as audio wearables handle calls, voice assistants, dictation and workplace communications.

There is no indication from Apple that the Beats Studio Buds flaw has been exploited in attacks against users. The company generally limits technical detail until patches are available, a practice intended to reduce the risk of copycat attacks before users can update their devices. The advisory, however, makes clear that the issue was serious enough to warrant a dedicated firmware release.

The broader supply-chain dimension is also important. When a flaw originates in a chipset vendor’s software or reference implementation, each device maker must test, package and distribute a product-specific update. That process can leave users exposed for varying periods depending on how quickly brands support older models and how reliably consumers receive firmware updates.

The article Apple closes Beats microphone security gap appeared first on Arabian Post.

The fix, released as Beats Firmware Update 1B211 on June 16, addresses CVE-2025-20701, a high-severity vulnerability tied to Bluetooth audio code used in the earbuds. The flaw affected Beats Studio Buds, a 2021 wireless earbud model sold under Apple’s Beats brand, and centred on how a Bluetooth audio device could be paired without the user’s consent under certain conditions.

The vulnerability did not require physical possession of the earbuds. An attacker would need to be within Bluetooth range and the device would need to be in a state where it was not yet paired and actively seeking pairing requests. That narrowed the window for exploitation, but the potential impact was significant because the microphone could be accessed without the user authorising the connection.

Apple said the issue involved open-source code and that Apple software was among the affected projects. The CVE entry was assigned by a third party. The vulnerability has been credited to Dennis Heinze and Frieder Steinmetz of ERNW GmbH, a Germany-based security consultancy that has examined weaknesses in Bluetooth audio chipsets and headphone firmware.

The flaw is linked to the Airoha Bluetooth audio software development kit, which is used in audio chips found in a range of wireless earbuds and headphones. Security researchers have warned that weaknesses in such components can spread across multiple consumer products because manufacturers often rely on shared chipset platforms, firmware modules and vendor-supplied software stacks.

CVE-2025-20701 has been described as an incorrect authorisation weakness that could permit unauthorised pairing of a Bluetooth audio device. In practical terms, the vulnerability sits at the point where convenience features, such as rapid or automatic pairing, intersect with authentication controls. If a device accepts a connection request without properly verifying the other side, an attacker can gain a foothold that should not be available.

The Beats update is being delivered automatically when the earbuds are paired with, and within Bluetooth range of, an iPhone, iPad or Mac. Users can check the installed firmware version through Bluetooth settings by selecting the information button next to the connected Beats Studio Buds. Owners using Android devices can update through the Beats app, provided the earbuds are paired and connected.

The episode underlines a wider security problem facing connected accessories. Earbuds, smartwatches, trackers and other peripherals are no longer passive add-ons. They contain microphones, radios, processors, memory and firmware that interact closely with phones and computers. A weakness in an accessory can therefore become a privacy risk even when the main handset or laptop remains fully patched.

Bluetooth’s short range can create a false sense of safety. Attacks usually require proximity, but the environments in which wireless earbuds are used — offices, airports, cafés, trains, conferences and classrooms — often place potential attackers close to targets. A flaw that can be triggered without user interaction is especially concerning because the victim may receive no obvious warning that a connection attempt has occurred.

Apple’s decision to publish a security note for a Beats firmware update also reflects a shift in how major technology companies handle accessory-level vulnerabilities. Firmware patches for headphones historically attracted less attention than updates for phones, laptops or browsers. That distinction is becoming harder to justify as audio wearables handle calls, voice assistants, dictation and workplace communications.

There is no indication from Apple that the Beats Studio Buds flaw has been exploited in attacks against users. The company generally limits technical detail until patches are available, a practice intended to reduce the risk of copycat attacks before users can update their devices. The advisory, however, makes clear that the issue was serious enough to warrant a dedicated firmware release.

The broader supply-chain dimension is also important. When a flaw originates in a chipset vendor’s software or reference implementation, each device maker must test, package and distribute a product-specific update. That process can leave users exposed for varying periods depending on how quickly brands support older models and how reliably consumers receive firmware updates.

The article Apple closes Beats microphone security gap appeared first on Arabian Post.

The issue, tracked as VU#457458 and made public on June 18, 2026, affects multiple UEFI applications signed by hardware and firmware vendors. The weakness does not rely on breaking encryption or stealing signing keys. Instead, it turns legitimate signed tools into attack instruments when those tools expose powerful pre-boot functions without adequate restrictions.

The risk centres on the trust model behind Secure Boot, a firmware security mechanism designed to ensure that only approved software runs during system startup. If a vulnerable application is signed by a certificate already trusted by a device, an attacker with sufficient access may be able to load it and use its functions to bypass Secure Boot policy. That could allow malicious code to execute before the operating system, endpoint protection tools and ordinary logging mechanisms are active.

The vulnerable applications include UEFI shell tools and boot-related components associated with several vendor ecosystems. Listed examples include applications tied to Acer, Acer Emdoor, ASUS, ECS, Getac, GIGABYTE, Toshiba, Uniwill, Maingear, Schenker and Maibenben, with exposed functions such as memory modification, variable dumping and firmware variable setting. One Acer-linked GRUB2 component is also identified in the affected list through its insmod functionality.

The discovery underlines a persistent supply-chain problem in firmware security: a signed binary can remain dangerous even when the signature is valid. Secure Boot checks whether a component is trusted, but a valid signature does not guarantee that the component cannot be abused. Where a signed pre-boot utility can manipulate memory, change non-volatile variables or load raw drivers, it can become a bridge from authorised execution to unauthorised control.

The attack resembles a “bring your own vulnerable driver” technique, adapted to the firmware layer. Such attacks have long troubled operating-system security, where adversaries introduce a legitimate but flawed signed driver to gain elevated privileges. At the UEFI level, the stakes are higher because successful compromise occurs before the operating system takes control.

The impact is limited to systems that trust the specific vendor certificate linked to the affected application. That qualification is important: the issue does not automatically expose every Secure Boot-enabled machine. However, enterprise fleets often contain mixed hardware, older firmware packages, recovery media and vendor utilities, making exposure difficult to rule out without checking DBX status and firmware inventories.

A successful exploit would require administrative privileges or physical access, but that threshold may not reassure high-risk organisations. Attackers who already have administrator-level access often seek persistence that survives reboot, reinstallation or conventional incident response. Firmware-level compromise can support that objective by allowing unsigned or malicious kernel components to load before normal security controls begin monitoring the system.

The recommended mitigation is to install vendor firmware and software updates and then update and verify the UEFI DBX, the revocation database used to block known unsafe boot components. Once the affected hashes or signatures are added to DBX, the vulnerable binaries should no longer execute during the boot process on protected systems.

The operational challenge is that DBX updates can be sensitive. Administrators must confirm that bootloaders, recovery images and deployment tools are compatible before revoking older components. A poorly sequenced update can cause boot failures, especially on systems using customised Linux boot chains, legacy recovery media or older signed utilities.

Vendor responses vary. GIGABYTE is listed as affected and has indicated it will remove a signed efiflash. efi component from BIOS update packages and restrict parameters that could be used through an EFI shell to bypass Secure Boot. AMD has said the identified impacted products have reached end of security support and declined to issue a CVE ID under its end-of-support policy. AMI, Intel and Supermicro are listed as not affected, while several major vendors remain in unknown status pending public statements.

The disclosure follows wider scrutiny of Secure Boot revocation practices after earlier vulnerabilities showed how outdated signed boot components could remain trusted for long periods. That pattern has pushed firmware security teams to treat DBX management as a continuing control rather than a one-off patching exercise.

For large organisations, the practical response is likely to involve three parallel tasks: identifying machines that trust affected certificates, ensuring firmware and bootloaders are current, and confirming that DBX updates have been applied successfully. Asset visibility will be central because vulnerable UEFI applications may be present in firmware packages, service partitions, recovery environments or administrator toolkits rather than installed operating-system software.

The episode also highlights a governance gap in the UEFI ecosystem. Hardware makers, firmware suppliers, operating-system vendors and security researchers all share responsibility for the trust chain, but revocation depends on coordinated updates reaching devices that may remain in service for years. As devices age and vendor support ends, signed pre-boot utilities can become difficult to revoke without disrupting compatibility.

The article Firmware trust gap widens over UEFI flaw appeared first on Arabian Post.

The campaign, tracked as GitBait, has been active for nearly three years and has impersonated at least a dozen banks and financial services providers. Its operators have used more than 100 GitHub Pages-hosted domains and repository structures to publish cloned landing pages under directory paths such as support, cancellation and mobile-banking variants, enabling them to keep parts of the network alive even when individual pages are removed.

The operation reflects a broader shift in financial phishing, where attackers are moving away from stand-alone malicious infrastructure and leaning on trusted cloud and developer platforms that already carry encryption, availability and reputational cover. GitHub Pages, a free static website hosting service, gives each page a github. io address and HTTPS protection, making crude blocklist-based defences less effective when victims are directed through text messages, email or chat apps.

At the centre of the campaign is a reusable phishing kit with an internal selector panel. Operators can choose the institution they want to mimic and generate a matching landing page, allowing the same infrastructure to serve multiple brands. The cloned pages are designed for both desktop and mobile users, reflecting the way banking customers in Mexico increasingly move between app-based and browser-based access.

Victims are typically taken through a staged process that begins with a trust-building imitation of a bank page and then moves into forms requesting credentials, card numbers, customer IDs and other sensitive fields. Some versions display a fake verification or waiting screen after submission, a tactic that keeps the user on the page and reduces suspicion while the information is transmitted elsewhere.

The most notable feature of GitBait is its serverless collection method. Instead of sending stolen data to a conventional command-and-control server, obfuscated JavaScript embedded in the phishing pages intercepts form submissions and pushes the data through the SheetBest API into attacker-controlled Google Sheets. This approach gives the operators a ready-made storage and viewing system without maintaining their own back-end infrastructure.

At least one variant used Telegram bot infrastructure as an alternative exfiltration channel, with hardcoded tokens and chat identifiers embedded in the page code. That suggests the operators have maintained backup routes for collecting data and have adjusted their workflow over time as hosting and detection pressures changed.

Repository activity linked to the operation points to organised maintenance rather than one-off abuse. Multiple operator accounts appear to have contributed to page deployment, brand template updates and infrastructure changes. Commit histories show work continuing over extended periods, indicating a campaign managed with the discipline of a repeatable fraud operation.

The use of crafted Open Graph preview tags added another layer of deception. When malicious links were shared through messaging platforms, the preview could display the name, logo or visual language of a targeted financial institution, increasing the likelihood that a customer would tap through without scrutinising the github. io address.

The phishing pages do not exploit a vulnerability in GitHub Pages. They abuse a legitimate publishing feature by placing deceptive content on a trusted platform. That distinction matters for defenders, because the risk lies less in software compromise and more in the speed with which attackers can create, modify and reissue pages that borrow the credibility of widely used services.

The case also highlights the limits of traditional brand-protection methods. Takedown requests can remove individual repositories, but modular hosting and duplicated page structures allow operators to relaunch quickly. Financial institutions now need continuous monitoring for naming patterns that combine their brands with support, cancellation, verification or mobile-banking terms, especially on free hosting and code-sharing platforms.

Security teams are being urged to watch for unexpected outbound browser traffic to api. sheetbest. com from banking-session contexts, as well as suspicious form submissions from pages outside authorised domains. Behavioural detection, transaction alerts, device fingerprinting and stronger customer authentication can help reduce losses when credentials have already been captured.

For customers, the warning signs remain familiar but harder to spot. A banking page reached through a message link, a request for full card details, or a demand to re-enter online-banking credentials outside a bank’s official app or domain should be treated as suspicious. The presence of HTTPS or a recognisable logo is no longer enough to establish trust.

The article GitBait phishing ring targets Mexican bank users appeared first on Arabian Post.

The plugins, listed under seven vendor accounts, were presented as coding assistants, code reviewers, bug finders, unit-test generators and Git commit-message tools. They invoked services familiar to developers using artificial intelligence inside IDEs, including OpenAI, DeepSeek and SiliconFlow. Combined marketplace download figures for the identified plugins were close to 70,000, with DeepSeek AI Assist and CodeGPT AI Assistant accounting for more than 53,000 of those downloads.

The campaign is notable because the malicious behaviour did not depend on a visibly broken or suspicious tool. The plugins offered chat, code review, bug detection, commit-message generation and test writing, giving users little reason to suspect that a credential-harvesting routine was running behind the settings panel. The theft was triggered when a developer pasted an API key into the plugin configuration and clicked Apply, a normal step for “bring your own key” AI tools.

Technical analysis found that the plugins used a shared codebase repackaged under different names and identifiers. Once a key was saved, the settings handler passed it to a hardcoded endpoint at 39.107.60[.]51 over unencrypted HTTP. The request included a static authentication value embedded in the plugin code, while the payload contained the user’s provider secret. That meant the key left the workstation before the developer had any indication that it was being sent anywhere other than the selected AI service.

The earliest known listing in the cluster appeared on 31 October 2025, when DeepSeek Junit Test was released. Other plugins followed through November, December, January, February and April, before a jump in June, when CodeGPT AI Assistant was released on 9 June and DeepSeek AI Assist on 10 June. Their download counts rose far above most earlier entries, although marketplace figures cannot be treated as a precise count of unique victims because downloads and ratings can be inflated.

The identified plugins include DeepSeek Junit Test, DeepSeek Git Commit, DeepSeek FindBugs, DeepSeek AI Chat, DeepSeek Dev AI, DeepSeek AI Coding, AI FindBugs, AI Git Commitor, AI Coder Review, DeepSeek Coder AI, AI Coder Assistant, DeepSeek Code Review, CodeGPT AI Assistant, DeepSeek AI Assist and Coding Simple Tool. Vendor accounts linked to the listings included CodePilot, StackSmith, CodeCrafter, CodeWeaver, JetCode, DailyCode and ZenCoder.

The attackers also appear to have built a paid tier into the operation. After payment through a donation wall, the remote server could return an API key to the user’s plugin, which would then use that key for model calls. The origin of those returned credentials has not been established, but the design raises the possibility of a two-sided abuse model in which credentials taken from one group of developers are reused or resold to another.

The incident underlines a widening security problem around AI-assisted development. IDE plugins sit inside environments that often contain proprietary code, project files, cloud credentials, tokens and build-system access. JetBrains’ Marketplace guidance says plugins run with the same access rights as the IDE, can connect to the internet, can interact with files and are not isolated through fine-grained permissions or sandboxing. Marketplace moderation combines automatic checks and review, but the case shows how a small exfiltration routine can be hidden inside a tool that otherwise behaves as advertised.

The risk is not limited to immediate billing abuse on AI platforms. A stolen API key can reveal usage patterns, expose application workflows, enable unauthorised model calls and create unexpected costs for the key owner. Where organisations use central accounts, a compromised key may also blur audit trails, making it harder to distinguish legitimate developer activity from attacker-driven consumption.

The article JetBrains plugin scam puts AI keys at risk appeared first on Arabian Post.

The June security update covers NeMo Framework versions from 0.0 through 2.7.2, with users advised to move to version 2.7.3 or later. The flaws are tracked as CVE-2026-24155, CVE-2026-24252 and CVE-2026-24228, each carrying a CVSS v3.1 base score of 7.8, placing them in the high-severity category. The bulletin marks the issue as important for all platforms, while two of the three weaknesses specifically affect Linux deployments.

The most operationally sensitive of the three is CVE-2026-24252, an OS command-injection weakness in NeMo for Linux. Such flaws matter because they can allow an attacker to pass crafted input to an application in a way that triggers unintended system commands. In shared AI infrastructure, where researchers, engineers and automated workloads may use the same GPU servers, a local low-privileged foothold can become a route to broader compromise.

CVE-2026-24155 is a code-injection vulnerability affecting NeMo Framework across all platforms. A successful exploit could lead to code execution, privilege escalation, information disclosure and data tampering. CVE-2026-24228 affects NeMo Framework on Linux and involves deserialisation of untrusted data, a class of vulnerability that has long been considered dangerous in machine-learning and software supply-chain environments because model files, checkpoints and intermediate artefacts often move between systems and teams.

NVIDIA credited Moomi Chen with reporting CVE-2026-24155 and CVE-2026-24252, while CVE-2026-24228 was credited to Tyler Zars working with Trend Micro’s Zero Day Initiative. The company’s update directs users to obtain the fixed version from the official NeMo repository and evaluate risk in line with their own configuration, reflecting the varied ways in which the framework is used across enterprise, academic and cloud environments.

NeMo is a widely used open-source framework for building, customising and deploying generative AI models. It supports work on large language models, multimodal systems, speech recognition, text-to-speech and other AI workloads. Its role in training and fine-tuning pipelines makes flaws in the framework more significant than ordinary application bugs, because AI development environments often hold model weights, training data, proprietary prompts, credentials, experiment logs and access to expensive compute resources.

The vulnerabilities arrive as organisations are moving from experimental AI deployments to production systems. That shift has increased scrutiny of model-development tooling, not only the models themselves. Security teams are focusing more closely on the software layers around AI pipelines, including Python packages, model checkpoints, dataset-processing scripts, notebook environments, orchestration systems and inference servers. NeMo sits within that broader risk landscape, where a weakness in development tooling can affect downstream production systems if compromised code or artefacts are promoted through a pipeline.

The attack requirements in the advisory indicate local access, low privileges and no user interaction. That profile does not describe an internet-wide remote bug, but it remains serious in multi-user and containerised AI environments. Many organisations consolidate training workloads on central GPU clusters, where a compromised user account, vulnerable notebook, exposed development container or poisoned internal workload could provide the access needed to attempt exploitation.

Security teams are expected to prioritise patching systems that run NeMo on shared Linux hosts, research clusters, model-training platforms and environments where untrusted or externally sourced model artefacts are handled. The fixed version also matters for teams that build custom containers around NeMo, since updating the source repository alone may not protect running workloads unless base images, dependency locks and deployment pipelines are rebuilt.

The disclosure follows a pattern of rising attention to AI framework security. Earlier vulnerabilities affecting model-loading, checkpoint handling and deserialisation across AI libraries showed how development tools can become an entry point for code execution. The NeMo bulletin reinforces a central lesson for enterprises adopting generative AI: model governance is incomplete without conventional software security controls, including dependency tracking, least-privilege access, code review, container isolation and rapid patch management.

For NVIDIA, the update comes at a time when its AI software stack is becoming more central to enterprise adoption of accelerated computing. The company’s hardware dominance has been matched by a growing set of frameworks, libraries and model tools designed to make AI development easier across cloud, on-premises and hybrid infrastructure. That broader software footprint also expands the security responsibilities around developer tooling.

Organisations running NeMo should identify affected installations, confirm whether versions up to 2.7.2 are present, update to 2.7.3 or later, rebuild dependent containers and review access controls on shared AI infrastructure. Teams handling third-party checkpoints, plug-ins, scripts or experimental model artefacts should apply additional caution, particularly where Linux-based training systems are shared across projects.

The article NVIDIA plugs NeMo flaws affecting AI pipelines appeared first on Arabian Post.

The move places artificial intelligence, cyber-physical security, critical infrastructure resilience, predictive risk management and next-generation fire protection at the centre of the Riyadh event, scheduled for 16–18 November 2026 at Riyadh Front Exhibition & Conference Center. Organisers expect the eighth edition to be the largest in the event’s history, with more than 25,000 visitors and over 500 exhibitors from across security, safety, fire and emergency services.

The Future Security Summit Advisory Committee includes representatives linked to the Royal Commission for AlUla, the Ministry of Municipalities and Housing, the International Civil Aviation Organization, Dubai Airports, IFPO MENASA, King Salman International Airport and specialist security consultancies. Its remit is to frame discussions on protecting public spaces, aviation systems, smart-city infrastructure, major events, logistics corridors and digital environments where physical and cyber risks increasingly overlap.

The Fire Protection & Technology Summit Advisory Committee brings together specialists from Saudi Aramco, Red Sea Global, Qiddiya City, King Fahd International Airport, AECOM, the National Water Company, NEOM and other fire and life-safety organisations. The committee’s work is expected to shape sessions on performance-based fire engineering, detection and suppression technology, emergency response, code compliance and protection of large-scale developments.

Riham Sedik, exhibition director of Intersec Saudi Arabia, said the committees bring together professionals with decades of operational, strategic and technical experience across security, emergency management, fire protection and resilience. Their role, she said, would help ensure that the summits address real operational challenges while giving delegates practical insight into the technologies, frameworks and leadership strategies shaping the sectors.

The advisory structure reflects a wider shift in the region’s risk environment. Saudi Arabia’s infrastructure pipeline spans tourism, aviation, energy, logistics, entertainment and urban development, with projects such as Red Sea Global, Qiddiya, NEOM, Diriyah and AlUla placing new demands on safety, security and business-continuity planning. The country is also preparing for Expo 2030 in Riyadh, the 2034 FIFA World Cup and the annual Hajj pilgrimage, each requiring layered security, crowd management, emergency response and transport coordination.

Yusuf Hasan, senior aviation security adviser at the International Civil Aviation Organization and a member of the Future Security Summit Advisory Committee, has identified the management of rapid growth while preserving secure, resilient and trusted environments as a key challenge for the region. He said artificial intelligence was accelerating the move from reactive protection to predictive, intelligence-led security through stronger threat detection, analytics and automation.

That emphasis is likely to feature prominently in the Future Security Summit, where themes include command-and-control systems, personal data protection, industrial control-system cybersecurity, crisis and emergency management, critical-infrastructure protection and protection of mega-events. The agenda also points to the increasing relevance of cyber-physical convergence, as airports, energy assets, real estate developments and public venues rely on connected surveillance, access-control, communications and building-management platforms.

Fire protection is moving through a similar transition. Dr Reginald D. Freeman, executive director for fire and emergency medical services at NEOM and a member of the fire summit committee, has said the sector is shifting from traditional code compliance towards risk-informed, performance-based fire engineering. He said the complexity of modern mega-projects required more sophisticated fire and life-safety approaches, with greater emphasis on anticipating risk and strengthening resilience rather than simply responding after incidents occur.

Market indicators underline the commercial stakes behind the conference agenda. Saudi Arabia’s security market is projected to reach about $3.4 billion by 2030, supported by demand for integrated physical security, cybersecurity, surveillance, access control and command-and-control solutions. The country’s fire and safety equipment market is projected to expand to about $7.1 billion by 2032 as construction, industrial development, regulatory enforcement and smart-building systems increase spending on prevention, detection and suppression technologies.

Intersec Saudi Arabia’s 2026 expansion follows the relocation of the event to Riyadh Front Exhibition & Conference Center and a planned 40 per cent increase in exhibition space. Organisers have positioned the show across five core sectors: commercial and perimeter security, homeland security and policing, cybersecurity, fire and rescue, and safety and health. The two CPD-certified conference streams are expected to convene more than 110 experts, policymakers and industry leaders.

The article Intersec Saudi panels set resilience and fire agenda appeared first on Arabian Post.

The incident affected OptinMonster, TrustPulse and PushEngage, products operated under the Awesome Motive umbrella and embedded on sites for pop-ups, lead generation, social proof alerts and push notifications. The compromise did not arrive through a normal plugin update. Instead, malicious code was appended to legitimate front-end scripts delivered through vendor-controlled content delivery network endpoints, meaning fully patched websites could still have loaded the poisoned files.

The injected script was designed to stay quiet for ordinary visitors. It activated only when a logged-in WordPress administrator loaded an affected page, then used that session to collect valid security tokens and make requests that looked like legitimate administrative actions. Once triggered, it attempted to create a new administrator account, install a self-hiding plugin and transmit credentials and site details to an attacker-controlled lookalike domain, tidio. cc, which mimicked the legitimate tidio. com brand.

The fixed operator account identified in the campaign was developerapi1 using the email customer1usx@gmail. com, while most observed attempts used randomised devxxxxxx administrator identities. The backdoor plugin rotated names, including “Content Delivery Helper” and “Database Optimizer”, and was built to hide from plugin lists, user lists, update checks and common dashboard views. It also exposed a web shell capable of running server commands and a separate code-execution endpoint.

The exposure window varied across products. Malicious code was seen in OptinMonster and TrustPulse script files late on June 12 UTC and was removed within a short window, while PushEngage’s affected scripts were served for several hours on June 12 and continued from some CDN edge locations into June 14. The companies have since said the altered files were removed, CDN caches purged and credentials rotated, but those steps do not remove backdoors already planted on customer websites.

OptinMonster has more than 1 million active WordPress installations, while PushEngage lists more than 9,000 active installations. OptinMonster’s own marketing says more than 1.2 million users rely on the service. WordPress remains the dominant content management system, powering about 41.5 per cent of all websites and 59.3 per cent of sites whose content management system can be identified, making plugin supply-chain incidents unusually wide in reach.

Vendor notices attributed the breach to an attacker gaining access to a marketing website server through a known vulnerability in UpdraftPlus, a backup and migration plugin, and then finding a CDN API key on that server. They said application servers, source code repositories and customer-data systems were hosted separately and showed no evidence of access. Security researchers have treated the initial entry point as still needing full corroboration, while agreeing that the critical abuse path was control over scripts delivered from trusted CDN locations.

The UpdraftPlus issue cited in the notices is tracked as CVE-2026-10795 and affects versions up to and including 1.26.4 in specific circumstances involving UpdraftCentral connections. It allows unauthenticated attackers to run remote procedure calls as a connected administrator, potentially uploading and activating malicious plugins. The flaw has been patched, but its appearance in the same chronology highlights the layered risk created when a plugin, a marketing site and a CDN key intersect.

Firewall telemetry from protected sites showed 271 blocked exploitation attempts across 13 websites over about 36 hours on June 14 and 15, from 81 unique IP addresses. Most attempts used the WordPress REST users endpoint, matching the payload’s effort to create an administrator account under cover of a genuine admin session.

The article WordPress plugin hijack plants hidden backdoors appeared first on Arabian Post.

The bug, tracked as CVE-2026-53435, affects Jenkins 2.567 and earlier and Jenkins LTS 2.555.2 and earlier. Fixed versions, Jenkins 2.568 and LTS 2.555.3, were issued on 10 June as part of a wider security update covering several core vulnerabilities. The flaw has been scored 8.8 on the CVSS 3.1 scale, placing it in the high-severity range.

The issue centres on how Jenkins processes attacker-controlled config. xml submissions. Jenkins uses XStream serialisation to load and save configuration and build data, guarded by a custom class filter intended to block unsafe deserialisation. The weakness allows an attacker to make Jenkins deserialise types from Jenkins core or installed plugins in a context that can later be reached through the Stapler web framework used for HTTP request handling.

That distinction matters for defenders. This is not a simple unauthenticated internet worm scenario based on the public advisory. The attacker needs Overall/Read permission and must either have a user account or hold permissions that allow a POST to config. xml, such as Item/Configure, View/Configure or Agent/Configure. Many development environments, however, grant broad read or configuration rights to engineering teams, contractors, service accounts and automation tools, widening the practical exposure.

Threat-intelligence accounts and security monitoring reports began flagging exploitation attempts against exposed Jenkins instances around 15 June. Honeypot activity described by researchers showed automated probing for Jenkins endpoints and attempts to plant malicious configuration data. Public proof-of-concept code also appeared after the advisory, accelerating the window in which defenders had to identify and patch affected controllers.

Successful exploitation could have consequences beyond a single build server. Jenkins often holds credentials, deployment keys, source-code access tokens and links to container registries, cloud environments and production release systems. A compromised controller can therefore become a staging point for supply-chain attacks, secret theft or tampering with build and deployment workflows, particularly in organisations that rely on automated release gates and shared administrative accounts.

The most serious path identified in the advisory involves user impersonation. Once an attacker can send HTTP requests as another user, the Script Console becomes a critical risk if the impersonated identity has administrative-level access. Jenkins’ Script Console can run Groovy code on the controller, making it a powerful administrative tool and a dangerous post-exploitation target.

A second impact is file access on the controller. Research examining the flaw showed exploit chains aimed first at predictable Unix files such as /etc/passwd, then at SSH keys, Jenkins credentials files and other secrets stored under the Jenkins home directory. Even when code execution is not achieved, file disclosure can give attackers enough material to move into source repositories, cloud accounts or internal services.

The June 10 update also addressed open-redirect flaws, a queue-item permission issue, limited user-profile information disclosure, stored cross-site scripting affecting node offline descriptions and a separate weakness involving plaintext secrets in configuration submissions. Although CVE-2026-53435 drew the strongest attention, defenders are being urged to treat the full advisory as a core platform update rather than a single-bug patch.

Security teams running Jenkins should prioritise version checks across all controllers, including development, staging and legacy build systems. Internet-facing instances carry the highest risk, but internal Jenkins servers are also attractive because attackers who already have a foothold often search for CI/CD platforms to obtain credentials and expand access.

Immediate containment steps include upgrading to Jenkins 2.568 or LTS 2.555.3, restricting access to controllers through VPNs or allow-listed networks, reviewing accounts with Overall/Read and configuration rights, and auditing Script Console use. Administrators should also review view, item and agent configuration changes made since 10 June, especially unexpected config. xml updates, newly created views, unusual HTTP POST activity and requests for sensitive files under the Jenkins home path.

The article Jenkins attacks expose CI pipeline risk appeared first on Arabian Post.

The campaign, tracked as SearchJack, shows how ordinary-looking browser tools can turn search traffic into affiliate revenue while giving users little practical visibility into who handles their queries. The extensions were presented as satellite imagery tools, map services, news readers, productivity aids and search helpers, but shared a common technical pattern: they used Chrome’s settings override mechanism to make their own search route the browser default.

Security researchers who mapped the operation identified 22 publishers and at least eight monetisation brokers linked through tracking parameters inside final Yahoo search redirect URLs. The affected extensions include high-install items such as PerfecTab Search, Quick Search Tool and Better Search, each listed at about 100,000 users, along with NewTab. Search at about 70,000 users and several map, video, menu and navigation-themed tools with smaller user bases.

The issue matters because search queries can reveal health concerns, financial worries, workplace activity, travel plans, political interests and login destinations. Once routed through third-party middleware, those queries may be logged alongside IP addresses, device identifiers and other technical data. The same control over traffic also creates an escalation risk: operators that can redirect search requests can later point users towards phishing pages, credential-harvesting sites or malicious downloads without needing to push a visible extension update.

The SearchJack findings underline a broader weakness in the browser-extension economy. Many extensions do not need broad permissions to change a user’s search path. Some in the campaign were minimal “shell” extensions, containing little beyond a manifest file and a default-search instruction. That simplicity can help them appear low-risk in static review because they may lack background scripts, content scripts or intrusive permission prompts.

Other extensions appeared to add just enough visible functionality to justify installation. Map viewers, video libraries and search-switching interfaces can make a product look useful while the main commercial activity happens through hidden redirect chains. Search Toggler, one of the named extensions, was flagged for a routing design in which user queries passed through operator middleware even when the interface suggested a choice of search engine.

Chrome’s documentation allows extensions to override selected settings, including search behaviour, but the Chrome Web Store’s policy framework places responsibility on developers to avoid misleading behaviour and respect user expectations. Users are also normally asked to confirm search-engine changes when an extension alters the default search setting. SearchJack raises questions over whether confirmation prompts and listing disclosures are enough when the commercial routing layer is buried behind technical parameters.

Checks of named Chrome Web Store listings show why the problem is difficult for users to judge. PerfecTab Search, listed with about 100,000 users, describes itself as a default search extension and states that it does not collect or use user data. Better Search, also listed with about 100,000 users, discloses handling personally identifiable information, web history, user activity and website content, while promoting Yahoo-powered results from the address bar.

The operation also highlights the role of brokers. Affiliate identifiers such as trp, infospace, flowsurf, adk, becovi, imageadvan, mnet, fc and dcola were linked to the search flows. This broker-led model means individual extensions can be removed or replaced while revenue relationships and hosted-search pathways continue elsewhere. For platform operators, that makes enforcement against single listings less effective than action against account clusters, domains and partner identifiers.

The article Chrome search hijack exposes 758,000 users appeared first on Arabian Post.

The claim, attributed to an online actor using the handle SHADOWBYT3$, centres on data allegedly connected to TINYpulse, an employee engagement and feedback platform associated with WebMD Health Services. The material is said to include workforce survey records, corporate email addresses, staff names, internal analytics, exported reports, workplace feedback, payment-related PDFs and W-9 tax forms. The allegation has not been confirmed by Nintendo or TINYpulse, and the available material does not prove whether Nintendo’s own systems were breached.

The incident claim surfaced on cybercrime channels with a deadline tied to mid-June, escalating pressure on the Kyoto-headquartered gaming group at a time when the company is managing heightened investor scrutiny around its console cycle. The actor’s post said the dataset contained reports from 2016 through 2026 and threatened disclosure if payment was not made. Security researchers who reviewed samples said parts of the material appeared consistent with internal employee engagement records, though the full dataset and method of access remain unverified.

The most sensitive element of the claim is not game source code or unreleased product material, but human resources information. Employee sentiment surveys and feedback platforms can contain candid remarks about management, morale, workloads and internal culture. Even where such systems are designed to support anonymous or confidential input, exported reports, metadata, email fields and administrator dashboards may create pathways to identify individuals if controls fail or data is mishandled.

The threat actor’s own language suggested the alleged target may have been data stored in or exported from TINYpulse rather than Nintendo’s core network. That distinction is significant. A direct breach of Nintendo infrastructure would raise questions about corporate defences, while a compromise through an HR technology vendor would place the case within the wider pattern of third-party cyber risk affecting large companies that outsource specialist workforce, payroll, collaboration and analytics functions.

Nintendo had not publicly confirmed the alleged incident at the time of writing. The company would be expected to conduct forensic checks, review vendor access logs, identify affected jurisdictions and determine whether employee or contractor notification obligations are triggered. TINYpulse or its parent organisation may also face questions about data segregation, authentication, administrator access, export controls and the retention period for older employee feedback records.

The alleged dataset size is modest compared with large entertainment industry leaks, but cybersecurity specialists generally treat HR records as high-risk because they can enable phishing, identity theft, social engineering and reputational pressure. W-9 forms may contain taxpayer identification details. Bank statement PDFs, if genuine, would raise the sensitivity of the incident further. Internal feedback and performance-related files can also expose private workplace grievances or management concerns that were never intended for public release.

The claim follows a shift in cyber extortion tactics away from disruptive encryption alone towards data theft and publication threats. Criminal groups increasingly target business applications holding sensitive but non-public information, especially where access to a vendor or cloud service can affect several clients. HR, payroll, legal, procurement and customer-support platforms are valuable because they often contain structured personal data, internal communications and documents that companies are under pressure to protect.

For Nintendo, the immediate commercial risk appears limited because there is no confirmed indication that consumer accounts, payment systems, live services, game development repositories or Switch 2 operations were affected. The reputational risk, however, could be material if the claim is validated, particularly for staff whose private feedback or financial documents may have been exposed. The company has historically been aggressive in protecting intellectual property, but workforce data incidents require a different response centred on privacy, notification and employee support.

Nintendo has dealt with cyber-related controversies before. In 2020, unauthorised access involving Nintendo Network ID credentials ultimately affected about 300,000 accounts, prompting password resets and changes to login options. A separate wave of development material leaks around the same period became known in gaming communities as the “gigaleak”, although that involved a different category of historic technical and product files.

The article Nintendo breach claim puts HR data at risk appeared first on Arabian Post.

The token’s sideways move followed a modest recovery of about 4 per cent over the past week, a gain that stood out against a cautious wider cryptocurrency market. Bitcoin and Ether also traded firmer, but investor conviction remained fragile after sharp swings across risk assets and thinner liquidity in several major digital tokens.

Market sentiment indicators have moved into unusually negative territory for XRP. One widely tracked measure of trader positioning showed average 30-day returns for active XRP holders deeply underwater, with losses at levels last seen during the late-2020 stress period. Such readings do not guarantee a rally, but they have often appeared near moments when forced selling eased and short-term rebounds developed.

The latest phase of fear has been amplified by weak price structure. XRP remains far below the levels reached during last year’s rally and has struggled to hold gains above key moving averages. Technical traders are watching the $1.18 to $1.20 area as near-term support, while resistance around $1.29 and then the mid-$1.30s could determine whether the bounce extends or fades into another consolidation phase.

Liquidity has become a central concern. Order-book depth on major venues has thinned from earlier cycle peaks, making XRP more vulnerable to sharp intraday moves when leveraged positions are unwound. That cuts both ways: a negative headline can trigger outsized selling, while crowded bearish positioning can produce abrupt recoveries if spot buyers return.

The backdrop is mixed rather than uniformly bullish. The Ripple-linked token has benefited from a clearer legal environment after the long-running securities case over XRP sales was formally brought to an end last year, leaving a $125 million penalty and restrictions tied to institutional sales in place. That outcome removed one of the largest overhangs for secondary-market trading, though it did not erase regulatory scrutiny around token issuance and institutional distribution.

Institutional interest has also helped cushion sentiment. XRP-linked exchange-traded products have continued to attract attention from asset managers and trading firms, creating a channel for regulated exposure that was largely absent during earlier cycles. Supporters argue that this has broadened the investor base beyond retail traders, while sceptics note that inflows can soften but not fully offset macro-driven selling when liquidity retreats across crypto markets.

Network developments have added another layer to the debate. The XRP Ledger’s version 3.2.0 software release has shifted the core server branding from rippled to xrpld and introduced infrastructure changes aimed at improving node efficiency. The update is not a consumer-facing catalyst, but it matters for validators, developers and service providers that rely on stable network operations.

For traders, the immediate question is whether negative crowd sentiment has reached exhaustion. Crypto markets frequently move against the most crowded view, and XRP has a history of sharp rallies after periods of intense doubt. Yet those rebounds have usually required more than pessimism alone. Stronger spot demand, improved liquidity and broader risk appetite have all played a role.

Broader conditions remain unsettled. Digital assets have been affected by shifting expectations for interest rates, volatile technology shares and uncertainty over institutional portfolio flows. Bitcoin’s recovery from its early-June lows has helped steady sentiment, but the market has not returned to the momentum seen during earlier bullish phases.

XRP’s supporters continue to point to its established settlement narrative, long operating history and developer ecosystem. Critics counter that adoption claims have often run ahead of measurable usage, and that token performance remains heavily dependent on speculative flows rather than network revenue or clear cash-flow fundamentals.

That tension is likely to define XRP trading in the days ahead. A sustained move above the upper end of the current range could force short sellers to cover and invite momentum buyers back into the market. Failure to hold support near $1.18 would weaken the rebound argument and expose the token to another test of lower levels.

The article XRP steadies as extreme fear fuels rebound hopes appeared first on Arabian Post.

The Stock Trading Carnival runs from 15 June to 4 July 2026 and is positioned as the third edition of the exchange’s Global Capital Gala series. The campaign allows eligible users to share rewards by inviting friends to trade stocks, taking part in trading activities and entering incentives aimed at first-time stock traders on the platform.

The Panama City-announced initiative gives users access to high-profile names including Nvidia, Micron, Samsung and SK Hynix, placing the campaign directly within the artificial intelligence and semiconductor investment theme that has dominated market activity this year. The inclusion of memory-chip leaders reflects strong demand for high-bandwidth memory, data-centre infrastructure and AI-linked computing capacity, areas that have pushed chip and storage stocks sharply higher.

BingX is presenting the campaign as part of a wider push beyond digital assets into traditional finance products. Its TradFi offering already covers more than 100 assets across commodities, foreign exchange, stocks and indices, with the company saying traditional-finance trading reached half of total platform volume at its peak during the first quarter. The exchange has also said peak daily TradFi volume has exceeded $2bn.

The move shows how crypto exchanges are trying to retain users who want exposure to equities, commodities and macro assets without shifting between brokerage and digital-asset accounts. The promise of near round-the-clock access remains one of the main selling points, particularly for users outside the trading hours of major stock exchanges.

Pablo Monti, a BingX spokesperson, said stock trading had become a key pillar of the company’s multi-asset strategy, reflecting demand from users seeking broader exposure beyond crypto. He said BingX TradFi was designed to make global markets easier to access while keeping the flexibility and user experience associated with the exchange.

The launch comes during a broader industry race to package traditional assets for crypto-native traders. Tokenised equities and stock-linked products have moved from niche experiments to a major competitive front, with exchanges and blockchain infrastructure firms testing models that track listed shares, private-company valuations or equity indices.

That expansion also brings regulatory and market-structure questions. Tokenised securities remain subject to securities rules when they represent stocks, bonds or similar instruments, even if ownership is recorded on a blockchain. Regulators have drawn distinctions between issuer-sponsored tokens, custodial models backed by underlying securities, and synthetic products that provide price exposure without the same ownership rights.

Mainstream market operators are also entering the field. Nasdaq has received approval for trading and settlement of certain tokenised securities, initially covering major liquid stocks and exchange-traded funds, while other exchange groups have explored blockchain-based settlement systems. That puts crypto platforms under pressure to show that their equity-linked products have clear backing, transparent terms and adequate investor protections.

BingX has been building its profile through several overlapping initiatives. The company, founded in 2018, says it serves more than 40m users worldwide and ranks among the leading global crypto derivatives exchanges. It has promoted copy trading, spot trading, futures and AI-powered tools as part of a broader effort to become a trading hub rather than a pure crypto venue.

Its first-quarter update highlighted more than 5m users of BingX AI products and 57m queries handled by its AI suite. The company has also used sports sponsorships to raise visibility, including its role as principal partner of Chelsea FC since 2024 and as the first official crypto exchange partner of Scuderia Ferrari HP in 2026.

The stock campaign follows other product pushes, including zero-fee TradFi futures and pre-IPO access initiatives. Those areas can attract traders looking for early exposure to high-demand companies, but they also carry risks around liquidity, pricing, leverage and whether instruments are directly backed by assets.

The article BingX expands stock trading push with carnival appeared first on Arabian Post.

The operation, tracked as Velvet Ant and labelled Operation Highland by investigators, exposed a high-risk tactic in cyber espionage: rather than relying only on conventional malware, the intruders replaced trusted OpenSSH binaries and Pluggable Authentication Modules with altered versions that could steal credentials, log commands and allow unauthorised entry.

The earliest forensic traces date to 2016, indicating an intrusion that persisted across years of system operation, security reviews and containment efforts. The targeted environment had no direct internet connectivity, a design meant to limit exposure, but the attackers built a staged path through internet-facing systems and then moved through connected corporate infrastructure to reach the restricted segment.

The case underscores a growing weakness in critical infrastructure defence. Many operators focus heavily on perimeter controls, endpoint alerts and patching, while authentication components, network appliances and legacy systems may receive less scrutiny. Velvet Ant appears to have exploited that gap by embedding access into the login process itself, making normal administrative activity difficult to distinguish from hostile surveillance.

Investigators found that the attackers first compromised public-facing servers and deployed a modified version of GS-Netcat, an encrypted reverse-shell tool. The binary was disguised as a legitimate system utility and configured to survive reboots through system startup mechanisms. A separate SOCKS5 proxy written in Perl helped route traffic through compromised hosts and support lateral movement.

The intrusion then used web infrastructure as a bridge. Nginx configurations were altered, and FastCGI wrappers were chained to execute commands on back-end systems. One custom tool, named to resemble a routine uptime utility, established SSH connections into the restricted network after receiving parameters through HTTP requests. This allowed the attackers to reach hosts that were not directly exposed online.

The most damaging stage involved control of the authentication layer. PAM sits beneath many Linux login flows, including SSH sessions, and OpenSSH provides the remote access channel used by administrators across server estates. By altering both, Velvet Ant gained visibility into logins and commands while preserving an appearance of normal operations.

Nine variants of a backdoored pam_unix. so module were identified. Some accepted a hardcoded backdoor password, bypassing normal checks. Others captured legitimate usernames and passwords as users logged in. Several versions appeared to have been compiled in different environments, suggesting a structured build process rather than an improvised intrusion.

The OpenSSH modifications were equally intrusive. Altered ssh, sshd and scp binaries captured credentials, recorded shell commands and stored logs in hidden directories. Some versions included a custom flag allowing the operator to disable its own logging, reducing the risk that investigators would later reconstruct attacker actions from the compromised tools. In some cases, timestamps were manipulated to make malicious files resemble older system artefacts.

The operation also showed why password resets and session termination may fail when attackers control the component that validates credentials. Resetting passwords before removing the malicious PAM and OpenSSH binaries could simply feed new secrets back to the intruder. That placed defenders in a difficult position: removing the backdoor was necessary, but replacing authentication components incorrectly could lock administrators out of live systems.

The remediation effort required careful host-by-host profiling because the environment contained multiple Linux distributions and versions. Systems without internet access could not pull clean packages directly from trusted repositories, while critical production requirements limited downtime. Replacement components had to be tested, moved into the restricted network through controlled channels and validated immediately after deployment.

Velvet Ant has been associated with earlier campaigns targeting infrastructure that sits outside routine monitoring. A 2024 case involved legacy F5 BIG-IP appliances used for persistence, while another involved exploitation of a Cisco NX-OS command-injection flaw affecting Nexus switches after attackers obtained administrator-level access. The pattern points to a preference for trusted network and system components that defenders may treat as stable background infrastructure.

The article Velvet Ant hid inside Linux login stack appeared first on Arabian Post.

Two alleged administrators were arrested in Georgia on 10 June after investigators targeted the platform’s clear web and dark web infrastructure, seized domains, blocked Telegram accounts and replaced AudiA6 and Dark2Web pages with law-enforcement seizure banners. The action struck at a service that investigators say operated as a trusted cash-out pipeline for criminal groups seeking to convert traceable cryptocurrency into funds that appeared clean.

The suspects, Ruslan Igorevich Tkachuk, 37, a Ukrainian national, and Alexander Vladimirovich Ledenev, 25, a Russian national, were living in Batumi, Georgia, when they were detained. Prosecutors in the Eastern District of Pennsylvania have charged them by criminal complaint with conspiracy to launder monetary instruments and sting money laundering. US authorities plan to seek their extradition.

The coordinated operation involved the US Secret Service, IRS Criminal Investigation, Europol, Eurojust and law-enforcement partners across Australia, Canada, France, Georgia, Germany, Iceland, Japan, Poland, Switzerland and the United Kingdom. Investigators searched three properties, took down 25 domains, seized more than 30 servers, froze cryptocurrency worth about €692,000 and seized more than €86,000 in digital assets. More than 80 vehicles and several properties in Georgia were also confiscated.

AudiA6 is alleged to have processed illicit funds between 2022 and 2025, with law-enforcement blockchain analysis tying the service to more than 15 international cybercrime investigations. The platform is said to have catered to ransomware operators, darknet market users and cybercrime services by offering rapid laundering through complex transaction chains. Customers allegedly sent stolen cryptocurrency to wallets controlled by the group and received cleaned funds back, often within about an hour, for commissions ranging from 3 per cent to 10 per cent.

Investigators also found more than 6,000 know-your-customer records linked to money mule accounts used to move funds through cryptocurrency exchanges. Those records suggest the laundering network relied on accounts opened with stolen, purchased or otherwise compromised identities, allowing criminals to exploit regulated exchange infrastructure while distancing themselves from the origin of the assets.

The case has exposed the role of specialist laundering brokers in sustaining ransomware, where the ability to cash out can be as important as the malware used to break into victim systems. Criminal groups increasingly depend on intermediaries able to move funds through mixers, exchanges, mule accounts and cross-border payment routes while frustrating attempts to link blockchain transactions to real-world identities.

Court documents say AudiA6 wallets received about 10,333 bitcoin, valued at roughly $389.7 million at the time of the transactions, since the service was launched in 2021. Of that amount, about 393.39 bitcoin, worth roughly $19.2 million at transaction-time valuations, allegedly came directly from known darknet markets, ransomware organisations, cybercrime services and other illicit sources, with more funds arriving indirectly from criminal activity.

The alleged operators are also accused of administering Dark2Web, a cybercrime forum used to advertise illegal services and connect actors across the underground market. AudiA6 was promoted there as a service capable of disguising the source of cryptocurrency that might otherwise be linked to criminal proceeds. The forum’s takedown widens the operation beyond a single laundering desk, hitting both the financial channel and one of the marketplaces that helped feed it clients.

The action followed an earlier arrest in Poland in September 2025. Investigators used electronic devices seized in that case to identify other people allegedly involved in the laundering network, while judicial coordination enabled measures across several jurisdictions before the June operation in Georgia.

The takedown fits a wider enforcement pattern aimed at the financial infrastructure behind ransomware rather than only the hacking groups themselves. Blockchain intelligence has allowed investigators to trace funds across public ledgers, but criminals continue to adapt by using mule networks, cross-chain transfers, nested services and private communications channels. Ransomware payments remained substantial in 2025 despite greater resistance from victims, while leak-site activity and opportunistic attacks kept pressure on companies, public bodies and critical service providers.

The allegations against Tkachuk and Ledenev have not been tested in court. If convicted in the United States, each defendant faces a maximum possible sentence of 20 years in prison. Georgian custody and extradition proceedings will determine the next stage of the case, while seized servers and financial records are expected to support parallel investigations into ransomware payments and cybercrime laundering routes across multiple jurisdictions.

The article AudiA6 takedown hits ransomware cash channels appeared first on Arabian Post.

The technique marks an operational evolution for the group, also known as Fancy Bear, Sofacy, Forest Blizzard and Pawn Storm. Long associated with intelligence collection against NATO governments, Ukraine, defence contractors, political organisations and critical infrastructure, APT28 is no longer relying only on cloud servers, rented hosting and bespoke implants. Its use of consumer and small-office routers gives it infrastructure that looks ordinary, sits close to intended victims and is harder for defenders to block at scale.

The activity centres on Ubiquiti EdgeRouters infected by MooBot, a Mirai-derived botnet family originally deployed by criminal operators against devices still using default or weak administrator credentials. Rather than build that network from the ground up, GRU-linked operators gained access to infected routers, installed scripts and binaries and repurposed the devices as an espionage platform.

Compromised EdgeRouters have been used to collect Net-NTLMv2 authentication material, proxy network traffic, host spear-phishing landing pages and stage custom Python tooling. Investigators found Bash scripts and Linux ELF binaries on targeted devices, including tools designed to exploit backdoored OpenSSH services and support credential theft. Some activity was linked to exploitation of Microsoft Outlook vulnerability CVE-2023-23397, used to leak authentication hashes to actor-controlled systems.

A court-authorised US operation, disclosed in February 2024, disrupted parts of the MooBot network by deleting malicious files from infected routers and changing firewall rules to block remote access by the operators. The action blunted one layer of the infrastructure but did not remove the wider problem: millions of routers remain poorly maintained, exposed to remote access or dependent on firmware that users rarely update.

The router pivot has since widened beyond MooBot. APT28-linked infrastructure has been tied to a DNS hijacking campaign known as FrostArmada, involving vulnerable MikroTik and TP-Link devices. Instead of infecting a victim laptop directly, the operators changed DHCP and DNS settings on compromised routers so connected phones, computers and office systems automatically sent selected lookups to attacker-controlled resolvers.

That approach enables adversary-in-the-middle attacks against web and email services. When a targeted user attempts to reach a login domain, malicious DNS responses can direct the connection through an interception node, where passwords, OAuth tokens and session data may be collected. Non-targeted traffic can still resolve normally, reducing the chance that users notice unusual behaviour.

The scale of the activity illustrates the appeal of unmanaged edge devices. During peak FrostArmada activity in December 2025, more than 18,000 unique IP addresses across at least 120 countries were seen communicating with the infrastructure. More than 200 organisations and about 5,000 consumer devices were identified as affected, with targets spanning government, defence, logistics, telecommunications, information technology, energy and third-party email services.

The campaign also shows how state-backed operators are blending criminal infrastructure, commodity devices and tailored intelligence requirements. APT28’s operators appear to cast a wide net, then filter the victim pool for accounts and organisations of value. This model reduces the need to place heavy malware on protected enterprise systems while creating access points through remote workers, small offices and suppliers outside central security monitoring.

For network defenders, the implications are uncomfortable. Blocking a known malicious server is simpler than identifying traffic proxied through residential or small-business IP addresses. Router forensics are often thin, logs may be unavailable, and many small-office devices sit outside routine patching cycles. Even when law enforcement takes down part of a botnet, abandoned devices can be re-compromised or folded into a new operational network.

The activity reinforces APT28’s broader pattern of adapting tradecraft without abandoning older methods. The group has continued to use credential harvesting, spear-phishing, webmail exploitation and custom implants alongside router-based infrastructure. Edge devices now act as a complementary layer, providing stealth, proximity and resilience for intelligence collection rather than indiscriminate disruption.

The article Routers deepen APT28’s espionage reach appeared first on Arabian Post.

Zscaler’s ThreatLabz 2026 Phishing and Initial Access Report says overall phishing volume fell by about 20% year on year for a second consecutive year, but the decline masks a shift towards campaigns built for speed, credibility and credential theft. The findings point to a cybercrime market moving away from broad “spray and pray” emails and towards polished lures that imitate routine business processes, exploit trusted brands and bypass traditional filters.

The report, released at Zenith Live in Las Vegas on June 10, draws on telemetry from the Zscaler Zero Trust Exchange covering 2025, supplemented by deception data gathered between October 2025 and March 2026. It identifies 413,524 AI-generated site instances, with 37,447 flagged as malicious. That figure, just over 9% of the total, shows how AI site builders are being used to produce fake portals, lookalike applications and malicious download pages at low cost.

Services businesses emerged as a major target, with phishing hits rising 65.5% from 330.9 million to 547.7 million. The sector’s exposure reflects customer support, billing, renewals, onboarding and document exchange, where urgent requests and external interactions can appear legitimate. Manufacturing and government also remained high-value targets, while Microsoft and Google continued to be among the most impersonated brands because enterprise identity systems offer a direct route into corporate networks.

Encryption has become central to this model. Zscaler found that 95.2% of phishing activity was delivered through encrypted channels, while 87% of malicious activity used HTTPS. That creates a blind spot for organisations that inspect email but lack deep visibility into web traffic. Attackers are using certificates, redirects and hosting infrastructure to make fraudulent sessions appear indistinguishable from ordinary browsing.

The more consequential shift is real-time compromise. Modern phishing kits, including adversary-in-the-middle and browser-in-the-middle tools, are designed not merely to collect passwords but to capture session cookies, authentication tokens and one-time codes during the login flow. That weakens conventional multi-factor authentication when users are tricked into entering credentials through an attacker-controlled proxy. Once a valid session is captured, criminals can move quickly before alerts or password resets take effect.

The report also highlights the reconnaissance stage that precedes many attacks. Deception telemetry recorded 89.9 million hostile interactions from 1.37 million unique attacker IP addresses over six months. More than 121,000 distinct AWS-hosted IPs were observed probing customer environments, illustrating how cloud infrastructure gives attackers scale and disposable resources.

The trend fits a broader pattern across the threat landscape. The 2026 Verizon Data Breach Investigations Report found that generative AI is bolstering attacks at multiple stages and that mobile threats are producing higher click rates than traditional email. The Anti-Phishing Working Group recorded more than 1 million phishing attacks in the first quarter of 2025, the highest quarterly level since late 2023. Academic research published in May 2026 showed that generative AI can automate personalised spear-phishing messages using public social media data.

The commercialisation of phishing kits is adding to the problem. Kits now bundle landing-page templates, evasion tools, bot filtering, brand impersonation and dashboards that track credential capture. Google this week filed a lawsuit in New York targeting the operators of the Outsider phishing kit, alleging that the service used AI tools to help create fraudulent sites and generated more than 1.5 million associated URLs between November and April. The action reflects pressure on technology companies to police misuse of cloud platforms and generative AI systems.

For security teams, the economics are changing. A lower number of phishing attempts no longer signals reduced risk if each campaign is better researched, better hosted and better timed. Defences built around inbox filtering and user awareness training remain useful but are no longer sufficient. Enterprises are being pushed towards phishing-resistant authentication, continuous session monitoring, encrypted traffic inspection, tighter identity controls and controls that limit lateral movement after a compromised account is used.

The article AI sharpens phishing despite lower volumes appeared first on Arabian Post.

The campaign targets Windows users with archives and documents framed as useful resources for artificial intelligence adoption, coding and marketing. One lure was presented as a developer guide for agentic coding with Claude Code, while other decoy titles referred to AI-ready data systems and marketing in the age of AI. The approach reflects a wider shift in cybercrime: attackers are no longer relying only on crude phishing attachments, but are packaging malware inside material that appears relevant to employees trying to keep pace with AI tools.

The infection begins with a compressed archive containing a shortcut file and hidden PDF files. The visible file appears harmless, but the shortcut launches an obfuscated command sequence using native Windows tools. Instead of calling an obvious executable, the command reads selected lines from one hidden PDF and treats the file as a container for staged malicious code.

That first stage extracts and runs PowerShell commands while suppressing visible windows and bypassing execution restrictions. The embedded script searches for concealed data markers inside the PDF, decodes Base64 content, applies PBKDF2 key derivation and AES-CBC decryption, then writes another PowerShell script into the user’s application data directory. The use of a benign-looking document as a storage layer allows the attack to conceal payloads away from conventional attachment scanning.

The next phase creates a working directory under a path designed to resemble a legitimate Windows diagnostics component. Additional payloads are extracted from the same PDF, including scripts and batch files with names imitating Realtek audio services. A clean decoy PDF is also opened to reassure the victim that the downloaded guide was legitimate, while the malicious chain continues silently.

Persistence is established through scheduled tasks carrying audio-related names, including tasks configured to run after infection, at user logon and, where permitted, at system startup or daily intervals. This gives the attackers repeated opportunities to regain control even after a reboot. The campaign also attempts to reduce forensic traces by using temporary logs that are deleted after execution.

A notable feature is the abuse of AutoHotkey as an execution layer. The recovered executables match legitimate AutoHotkey binaries but are renamed to resemble Realtek components. Malicious logic is placed in AutoHotkey scripts, allowing the attackers to mutate scripts more easily and reduce dependence on custom compiled files that security tools may flag.

The loader reconstructs payloads from disguised text files and injects them into legitimate. NET Framework processes through process hollowing. It uses standard Windows API functions for creating suspended processes, allocating memory, writing malicious code and resuming execution, allowing the final payload to run under the cover of trusted system components.

The final stage includes a modular remote access trojan and AsyncRAT. The malware can contact command-and-control infrastructure, collect system details, identify the user and operating system, monitor security products, capture screen data, receive encrypted commands, load additional. NET assemblies directly in memory and run follow-on payloads. One AsyncRAT sample used a command-and-control address at 107.172.10.190, while related infrastructure included domains designed to resemble shampoo or cosmetics websites.

AsyncRAT remains attractive to attackers because it is open-source, flexible and widely adapted across criminal operations. Once installed, it can support remote desktop access, credential theft, file manipulation, command execution and further malware delivery. Its availability has made it common in phishing, loader and malware-as-a-service ecosystems.

The campaign also points to possible AI-assisted malware development. Several scripts contained Simplified Chinese variable names, structured comments and artefacts that appeared unsanitised, including an emoji-marked instruction line. The overall attack logic still suggests deliberate human planning, but the coding style indicates that generative tools may have helped speed up implementation.

The timing is significant as workplaces continue to adopt AI assistants, code-generation tools and prompt-based workflows. Developers, marketers, analysts and students are searching for guides, templates and utilities, creating a fertile environment for malicious downloads disguised as educational material. Similar operations have used fake AI websites, spoofed coding tools, malicious search advertisements and poisoned software recommendations to target users seeking productivity tools.

The article Fake AI guides mask AsyncRAT campaign appeared first on Arabian Post.

The /security-review slash command, introduced as an experimental public preview for GitHub Copilot CLI, allows developers to run an AI-driven security check inside the terminal. The feature is designed to inspect current code changes and flag weaknesses such as injection flaws, cross-site scripting, unsafe data handling, path traversal and weak cryptography before the code enters a shared repository or production pipeline.

The move reflects a broader shift in software security: catching flaws at the point of creation rather than waiting for pull request reviews, continuous integration scans or post-deployment audits. With developers increasingly using AI coding assistants to generate, refactor and test software, platforms are under pressure to embed guardrails into the same workflows that now produce large volumes of code.

GitHub Copilot CLI, which became generally available earlier this year, gives developers access to Copilot from the command line for tasks such as explaining code, debugging, editing files and opening pull requests. The new security review option builds on that terminal-first workflow by giving teams a lightweight check before a commit is made. Unlike traditional code scanning systems that rely on rule-based analysis and data-flow tracking across a repository, the new command uses large language model inference focused on the developer’s active changes.

That distinction is central to GitHub’s positioning of the feature. The tool is not being presented as a replacement for CodeQL, dependency scanning, secret scanning or manual security review. It does not perform CVE database matching, full dependency analysis or exhaustive repository-wide taint analysis. Its value lies in immediacy, giving developers a prompt warning when a proposed change appears to introduce a risky pattern.

The timing is significant for security teams facing faster development cycles and wider use of autonomous coding tools. AI assistants can accelerate software delivery, but studies of AI-generated code have repeatedly found that generated snippets may contain common weaknesses, including insecure input handling, poor randomness, unsafe deserialisation and improper output encoding. The risk becomes sharper when teams adopt agentic workflows that allow tools to edit multiple files, run commands and suggest architectural changes with limited human intervention.

Security specialists have long argued that “shift left” programmes work only when controls are embedded naturally into developer routines. Pre-commit checks are attractive because they reduce the cost of remediation; a flaw found before commit is easier to fix than one discovered after a build fails, a pull request is blocked or an incident response begins. The challenge has been balancing speed with accuracy, as noisy alerts can cause developers to bypass or ignore tooling.

The new Copilot command attempts to address that by offering targeted feedback on changed code rather than broad security reports. In practice, it may help identify obvious missing validation, suspicious string concatenation in database queries, improper file path construction, weak cryptographic choices or unsafe rendering of user-controlled content. Its usefulness will depend on how clearly it explains findings, how often it avoids false positives and whether developers treat its output as an aid rather than a definitive audit.

The public preview label is important. Experimental AI security checks can miss vulnerabilities, misclassify benign code or offer incomplete remediation advice. Large language models are also sensitive to context: a change that appears unsafe in isolation may be protected elsewhere, while a subtle flaw may require deeper knowledge of the application, framework or deployment environment. For regulated industries and large enterprises, such tools are likely to supplement rather than replace established application security testing.

GitHub’s broader security stack already includes CodeQL-based code scanning, secret scanning, push protection and dependency alerts. The terminal command adds another layer at the earliest point in the workflow. Used properly, it may reduce the number of avoidable issues that reach pull requests, giving formal scanners and human reviewers more room to focus on complex risks.

The feature also intensifies competition among AI coding platforms. Developers are comparing not only code generation quality but also review, testing, security and automation capabilities. Vendors are racing to add specialised agents and slash commands that can perform narrowly defined tasks inside familiar environments, from integrated development environments to terminals and repository workflows.

The article Copilot brings security checks to terminal appeared first on Arabian Post.

Tenet Security researchers have described a technique they call “agentjacking”, in which a hostile actor plants malicious instructions inside a fake software error report and waits for a coding agent to read it during routine debugging. The attack does not require stolen passwords, malware on the developer’s machine or direct compromise of the target company’s systems. Its force comes from turning trusted workflow data into instructions that an agent treats as part of its task.

The proof-of-concept centres on Sentry, a widely used application monitoring platform that collects software errors, stack traces and diagnostic messages. Many websites expose a Sentry Data Source Name so front-end errors can be sent to the correct project. That design is not, by itself, a security flaw. Tenet’s argument is that a coding agent connected to the issue-tracking workflow may read attacker-supplied diagnostic text and interpret it as guidance for fixing a bug.

Researchers said a crafted event could look like a normal error report, complete with apparently helpful remediation steps. When an AI coding agent is asked to investigate the issue, it may follow those steps, install a package, run a command or modify code. If the agent has terminal access, repository access or local environment privileges, the attacker’s instructions can move from a text field into executable action.

Tenet said it tested the method under controlled conditions across more than 100 agent deployments and identified exposure among more than 2,300 organisations. The company said the pattern bypassed conventional controls because the activity appeared authorised: the agent was using permitted tools, acting under a developer’s identity and performing what looked like legitimate debugging work. That is why the researchers describe the weakness as an “authorised intent chain” rather than a conventional intrusion path.

The finding sharpens concern over the way coding agents are being added to developer environments. Tools such as Claude Code, Cursor, Gemini CLI, GitHub Copilot-style assistants, Cline and other agentic coding products increasingly move beyond autocomplete into planning, editing, testing and command execution. Their usefulness depends on access to repositories, terminals, package managers, logs, tickets and continuous integration systems. Those same connections create a wider attack surface when the model cannot reliably distinguish data from instructions.

Prompt injection has already been ranked as a leading risk for large language model applications because malicious or hidden input can alter an AI system’s behaviour. Coding agents raise the stakes because they can act on that altered behaviour. A poisoned bug report, dependency instruction, README file, support ticket or pull request comment may become an operational command once an agent ingests it.

Security researchers have warned throughout 2025 and 2026 that agentic systems are vulnerable to tool abuse, indirect prompt injection, data exfiltration and sandbox escape. Academic work on coding-agent attacks has also shown that poisoned “skills”, hidden scripts and manipulated tool descriptions can steer agents into unsafe behaviour even when the user’s original instruction is benign. The Tenet case adds a practical enterprise workflow to that list: error monitoring.

The Sentry angle is significant because error telemetry is routinely treated as diagnostic evidence rather than hostile input. Client-side reporting systems are designed to accept events at scale, and developers often rely on them to triage production failures quickly. If an agent is placed between the error report and the fix, the contents of the report become part of the model’s working context.

The risk is not limited to one monitoring platform. Any system that accepts outside-controlled text and later feeds it to an agent can become an entry point. That includes customer support systems, crash reports, GitHub issues, project-management tickets, chat logs, documentation sites and code comments. The common weakness is not the external system alone, but the decision to let an autonomous agent consume untrusted content while retaining permission to execute commands.

Defensive advice is moving away from simple prompt warnings. Telling an agent to ignore untrusted text may not be sufficient if the malicious instruction is embedded in a context that looks operationally relevant. Security teams are instead being urged to treat agents as privileged digital identities, restrict their permissions, isolate their execution environments, require human approval for risky commands, block automatic package installation, inspect tool calls and keep detailed audit logs of agent decisions.

The article Fake bug reports expose coding agents appeared first on Arabian Post.

The spread of so-called shadow AI has exposed a familiar weakness in corporate cybersecurity: organisations that struggled to control unapproved apps, unmanaged cloud storage and personal messaging channels are now facing the same problem with tools that can absorb sensitive data, generate code, summarise contracts and automate decisions. The difference is scale. A single prompt can contain customer records, source code, financial forecasts, legal advice or board material, while the resulting output may be copied into business workflows with little record of how it was produced.

The issue has moved from a technology-management concern to a board-level risk. Surveys of enterprise technology leaders show that many are accountable for AI systems they do not fully control, while governance frameworks remain incomplete. AI incidents requiring human intervention are already being reported across large organisations, including data exposure, compliance breaches and cascading system failures when automated tools interact with live systems. The risks rise further as companies move from simple chatbots to AI agents that can execute tasks across email, customer platforms, code repositories and enterprise applications.

Security teams say the roots of the problem are not new. Many organisations still lack reliable software inventories, consistent data classification, strong identity controls and clear accountability for business-led technology procurement. Shadow AI exploits those same gaps. Employees often use unauthorised tools because approved systems are unavailable, slow to access or poorly suited to their work. Attempts to block popular AI platforms without providing alternatives can push usage into personal accounts, unmanaged browsers and consumer subscriptions, where logs, retention settings and contractual safeguards are weaker.

The acceleration of workplace AI has left policy trailing behaviour. Knowledge workers are using generative tools for drafting, research, translation, coding, spreadsheet analysis, presentation design and customer communication. In many cases, the productivity gains are real, making blanket restrictions hard to defend. But informal adoption creates uncertainty over whether confidential data is used to train external models, whether outputs are accurate, whether copyrighted material is being reproduced, and whether regulated information is being processed outside approved jurisdictions.

Regulators are also sharpening scrutiny. The EU AI Act, GDPR, sectoral financial rules and privacy laws in several jurisdictions are forcing companies to document how AI systems are selected, assessed, deployed and audited. High-risk uses, including credit, employment, healthcare, insurance and critical infrastructure, demand stronger evidence of oversight. Even where a tool is used only for internal productivity, companies may still face legal exposure if personal data, trade secrets or client material are entered into platforms without proper safeguards.

The key players in the corporate AI market are trying to close the gap. Microsoft is embedding Copilot across Microsoft 365 and enterprise security products, OpenAI is expanding business controls for ChatGPT, Anthropic is positioning Claude for enterprise use, and Google is integrating Gemini into Workspace and cloud services. Cybersecurity vendors are adding AI usage discovery, browser controls, data-loss prevention, prompt monitoring and model-risk dashboards. Yet tools alone are unlikely to solve a governance failure that is partly organisational.

A more mature response starts with discovery. Companies need to know which AI tools are being used, by whom, for what purpose and with what data. That requires browser telemetry, identity logs, expense analysis, cloud access security controls and staff surveys, combined with a non-punitive reporting culture. Workers are less likely to hide usage if they are offered approved alternatives and clear rules on what can and cannot be shared.

Data governance is the next weak point. Many businesses have not classified information accurately enough to apply meaningful AI controls. Without clear labels for public, internal, confidential, regulated and restricted data, security teams cannot enforce prompt-level policies or decide which use cases require human review. AI governance therefore depends on the same data discipline that cybersecurity leaders have been urging for years.

The rise of AI agents makes the challenge more urgent. Unlike chat tools that respond to single prompts, agents can plan tasks, call APIs, retrieve files, send messages and update systems. That makes identity and access management central to AI safety. Each agent needs a defined owner, approved purpose, restricted permissions, logging, expiry rules and emergency shut-off. Treating agents as ordinary software scripts leaves organisations exposed to privilege misuse, prompt injection, data leakage and untraceable decisions.

The article Shadow AI widens corporate control gaps appeared first on Arabian Post.

The flaws affect versions before phpBB 3.3.17, released on June 6 as a maintenance and security update for the 3.3. x branch. One issue exposes default installations using database authentication, while the other affects boards where administrators have enabled OAuth login through providers such as Google, Facebook or Bitly. The disclosures have raised concern because phpBB remains widely used by communities, hobby groups, support forums, companies and private boards that often contain years of user records, private messages and moderation history.

The more severe flaw, tracked by researchers as PTT-2026-004 while a CVE identifier remains pending, has been rated critical with a CVSS score of 9.4. It allows an unauthenticated attacker to obtain a valid session as any active user by sending a single crafted request. The attack does not require the victim’s password, prior access to the forum or any action by the targeted user. Versions up to and including phpBB 3.3.16 and phpBB 4.0.0-a2 are affected when the platform is using its default database authentication setting.

The second issue, tracked as PTT-2026-005, has been rated high with a CVSS score of 8.3. It stems from a weakness in phpBB’s OAuth account-linking process, where a logged-in victim who loads a crafted URL can have an attacker-controlled OAuth credential silently attached to the victim’s account. Once the binding is created, the attacker can log in through that OAuth provider without needing the victim’s password. The risk is narrower than the default authentication bypass because it requires OAuth to be configured, but the exploit path is notable because it can be triggered without a visible click if the URL is embedded in content that a browser loads automatically.

The OAuth flaw can be delivered through an image tag placed in a post or private message. When a logged-in user views the content, the browser requests the attacker’s URL in the background, completing the account-linking action without the victim’s consent. The attacker then gains persistent access through the linked OAuth account unless the entry is removed from the forum’s OAuth account table or noticed and revoked.

For ordinary users, a successful compromise could expose private messages, restricted boards, profile data and posting rights. For moderators or administrators, the impact could include access to private forums, moderation controls and the ability to act under trusted identities. phpBB’s Administration Control Panel still requires password re-authentication, which limits direct administrative escalation through OAuth alone, but forum-level access under a privileged account could still allow significant disruption and data exposure.

The disclosure timeline has intensified scrutiny of patching windows. The flaws were discovered on May 13, reported to the phpBB security team on June 4, fixed in phpBB 3.3.17 on June 6 and publicly detailed on June 8. That short interval places pressure on forum owners to move quickly, particularly where public member lists make username discovery easy or where old boards are maintained with minimal technical oversight.

Administrators running affected versions have been told to upgrade to phpBB 3.3.17 or later. For boards that cannot patch immediately and have OAuth enabled, disabling OAuth authentication and reverting to database authentication removes exposure to the OAuth chain until the update is completed. Operators are also being advised to audit OAuth account records for unexpected provider links, especially on administrator, moderator and high-profile user accounts.

The case highlights a broader security challenge in mature open-source platforms: extensions, authentication options and legacy deployment patterns can turn small logic flaws into account-takeover paths. OAuth remains a standard login mechanism across the web, but weak state validation, silent account linking and inadequate confirmation prompts have repeatedly produced serious vulnerabilities in web applications.

The article phpBB rushes patch for silent account hijack appeared first on Arabian Post.

The campaign marks a shift in social engineering from email inboxes and fake websites to short-form video feeds, where attackers mimic creator culture, use casual language and rely on platform algorithms to amplify content. Videos typically advertise cracked or “activated” versions of popular products such as Spotify Premium, CapCut Pro, Microsoft 365, Adobe tools and streaming services, targeting users who are searching for shortcuts to paid software.

The tactic works because it blends entertainment, instruction and fraud into a familiar format. Some clips show step-by-step “how-to” guides, while others are presented as ordinary user recommendations. Viewers are encouraged to visit external links, paste commands into Windows tools, download archives or disable security controls. The final payload can include information-stealing malware designed to harvest browser passwords, session cookies, cryptocurrency wallet data, saved files and account credentials.

Security teams tracking the activity have linked parts of the campaign to infostealer families such as Vidar and StealC, while related short-video and fake activation schemes have also been associated with Lumma and other malware-as-a-service operations. These tools are widely traded in underground markets, allowing low-skilled operators to buy access to malware infrastructure and focus on distribution through social platforms.

The use of TikTok and Instagram Reels gives attackers several advantages. Short videos are fast to produce, easy to repost and difficult for ordinary users to assess. Fraudulent clips can gain credibility through comments, likes, captions and copied visual styles. Attackers can also rotate accounts and links, making takedowns less effective when the same lure is quickly republished under a different profile.

The method builds on the “ClickFix” style of attack, where users are tricked into running commands themselves under the belief they are solving a software activation problem, bypassing a warning or completing a verification step. Instead of exploiting a technical vulnerability, the attacker exploits trust, urgency and the appeal of free access. That makes the campaign harder to block purely through patching.

The risk is highest for Windows users because many of the instructions rely on PowerShell, Windows Run or terminal commands. Once executed, the script can contact remote servers, download additional payloads and establish persistence. In some cases, the malware avoids obvious installation prompts, giving victims little indication that credentials and browser data are being copied.

Businesses face a wider threat from the same activity. A compromised personal device can expose work passwords, cloud tokens or browser sessions used for corporate services. Infostealer logs are routinely sold or exchanged, and stolen credentials have become a common entry point for ransomware groups, business email compromise gangs and account takeover operations.

The campaign also reflects a broader trend in cybercrime: attackers are following audience behaviour. As younger users and creators spend more time inside short-video apps, malicious actors are adapting their delivery methods to match the way people search for software tips, editing tools, AI utilities and entertainment hacks. The lure is often framed around productivity or creativity, not only piracy.

Platform operators have policies against malware promotion, deceptive links and account abuse, but short-form video moderation remains a difficult problem. A clip may not contain malware itself; it may only display instructions, refer viewers to a profile link or direct them to a changing third-party page. That separation between content and payload complicates automated detection.

The article Short video scams widen malware threat appeared first on Arabian Post.

The vulnerability, named RoguePlanet by its publisher, was released with proof-of-concept code under the alias MSNightmare, adding to a turbulent sequence of Windows and Defender disclosures that have tested Microsoft’s patching process and the wider debate over vulnerability disclosure. The issue has not yet been assigned a public CVE, and Microsoft had not issued a dedicated advisory for RoguePlanet at the time of review.

RoguePlanet is described as a race-condition flaw in Microsoft Defender that can, when successful, spawn a command prompt with NT AUTHORITYSYSTEM privileges. That level of access is among the most serious outcomes for a local privilege-escalation flaw because it can allow an attacker who already has a foothold on a machine to disable protections, tamper with files, deploy additional payloads or move deeper into a network.

The proof-of-concept was published on GitHub and includes C++ code and a compiled executable. The repository states that the exploit has been tested on Windows 11 official and Canary builds, as well as Windows 10 systems with June 2026 patches installed. The publisher described the exploit as inconsistent across machines, saying it reached full reliability on some systems while failing or requiring repeated attempts on others.

A third-party security firm said it had reproduced the exploit on a fully patched Windows 11 system carrying the June update, lending weight to the claim that the issue affects current builds rather than only outdated installations. The same analysis indicated that application allowlisting could block execution of the public proof-of-concept, although that does not remove the underlying software weakness.

The immediate risk is greatest where attackers already have local access through stolen credentials, malware, exposed remote access tools or another exploit chain. Local privilege-escalation bugs are rarely the first step in an intrusion, but they are often decisive in turning limited access into full compromise. For enterprise defenders, that makes RoguePlanet important even before a formal severity score is published.

The disclosure comes after a busy patch cycle for Microsoft. The June 2026 Patch Tuesday release addressed 200 vulnerabilities, including three publicly disclosed zero-days and 33 flaws rated critical. That volume has increased pressure on administrators already managing emergency Defender updates issued in May after two separate Defender vulnerabilities were added to the US known-exploited list.

One of those May flaws, CVE-2026-41091, involved improper link resolution before file access in Microsoft Defender and allowed local privilege elevation. It carried a CVSS score of 7.8 and affected Microsoft Malware Protection Engine versions before 1.1.26040.8. The second, CVE-2026-45498, involved denial-of-service conditions in Defender components. Both were treated as exploited vulnerabilities and carried urgent remediation deadlines for federal systems.

RoguePlanet appears to sit within the same broader pattern: security products that perform privileged file operations can become attractive targets when their own handling of links, mounts, symbolic paths or remediation actions is flawed. Defender runs with elevated authority because it must inspect, quarantine and manipulate files across the operating system. That privileged role gives attackers a high-value target if they can influence what the service opens, moves or rewrites.

The MSNightmare repository claims the exploit does not work as written on Windows Server because standard users cannot mount ISO images, while asserting that server editions may still be vulnerable if the technique is redesigned. That server claim remains unverified and should be treated cautiously until Microsoft or independent researchers publish additional analysis.

The disclosure has also revived friction between Microsoft and independent researchers. The same researcher persona has been linked to earlier public releases involving Defender and other Windows components, including BlueHammer, RedSun, GreenPlasma and YellowKey. Some of those were later addressed through security updates, while the publication of working exploit code before coordinated patch availability drew criticism from parts of the security community.

For organisations, the practical response is to verify that Defender engine, platform and security intelligence updates are current, review endpoint telemetry for unexpected SYSTEM-level shells, and restrict execution of unsigned or unapproved binaries. Microsoft’s current Defender security intelligence page lists engine version 1.1.26050.11 and platform version 4.18.26050.15 as the latest available line at the time of review, underscoring the need to check component versions rather than rely only on monthly operating-system patch status.

Security teams should also harden standard-user environments, limit local administrator rights, monitor suspicious mount activity, and test controls against privilege-escalation attempts. Application control, attack-surface reduction rules, endpoint detection coverage and rapid isolation procedures can reduce the chance that a local flaw becomes a domain-wide incident.

The article Defender flaw exposes Windows systems to takeover appeared first on Arabian Post.

The latest wave adds 23 malicious PyPI package-version artefacts to an operation already linked to Mini Shai-Hulud, Miasma and Hades activity. The broader campaign now spans hundreds of npm and PyPI artefacts, with security tracking indicating 471 affected artefacts across the two ecosystems, including 411 npm artefacts across 106 packages and 60 PyPI artefacts across 37 packages. The expansion shows that attackers are no longer relying on a single infection path, but are adapting delivery methods to reach developers, machine-learning teams, bioinformatics users and organisations building tools around model context protocol workflows.

PyPI is widely used by Python developers to distribute and install software libraries. Its trust model depends heavily on package maintainers, version integrity and developer judgement. That makes it an attractive target for supply-chain attackers seeking access not just to individual machines, but to the credentials and automation tokens that allow code to be published, deployed or integrated into production systems.

The Shai-Hulud-linked activity is notable for its cross-ecosystem behaviour. Earlier waves targeted npm, the JavaScript package registry, before moving into PyPI and other developer repositories. The latest PyPI infections include techniques designed to run silently during installation or Python start-up, allowing malicious code to execute before a developer notices anything unusual. Some poisoned wheels abuse Python startup hooks by bundling. pth files that trigger execution automatically, while others use native extension or loader-based approaches to start a credential-stealing payload.

A key feature of the campaign is its use of Bun, a JavaScript runtime, as an execution engine. Instead of assuming that Node. js or another local runtime is available, the malware can download Bun and use it to run heavily obfuscated JavaScript payloads. That cross-runtime design makes detection more difficult because defenders watching only Python execution paths may miss the transition into JavaScript-based behaviour.

Once executed, the malware attempts to harvest sensitive material from developer environments, including GitHub tokens, package registry credentials, cloud keys, SSH material, API keys and CI/CD secrets. Those credentials can allow attackers to publish further poisoned packages, access private repositories, alter build pipelines or exfiltrate code and configuration files. The worm-like logic gives the operation the potential to move from one compromised developer workstation into wider organisational infrastructure.

The latest activity also shows evidence of branding and marker changes across variants. The Hades naming convention has appeared in exfiltration markers and repository descriptions, while Miasma activity has been linked to broader Shai-Hulud-style tradecraft. Although attribution remains uncertain, some earlier Mini Shai-Hulud waves have been associated by security vendors with TeamPCP, a financially motivated threat actor that emerged in late 2025 and has been linked to attacks exploiting developer infrastructure.

The campaign builds on a sequence of attacks that unfolded through April, May and June 2026. PyPI package lightning versions 2.6.2 and 2.6.3 were identified as malicious on April 30 and quarantined the same day. The package is heavily used by AI and machine-learning developers, with roughly 8 million monthly downloads, magnifying potential exposure for teams that imported affected versions before removal. Other waves affected well-known developer projects including TanStack, Mistral AI, UiPath, OpenSearch and Guardrails AI.

The May phase of the campaign showed larger-scale npm compromise, with more than 170 packages affected and hundreds of millions of monthly package downloads connected to impacted projects. Known PyPI artefacts in that phase included mistralai version 2.4.6 and guardrails-ai version 0.10.1, both linked to payloads designed to steal development secrets and potentially enable lateral movement. Malicious packages were uploaded in waves on April 29 and May 11, before further PyPI discoveries emerged in June.

For organisations, the risk is greater than ordinary endpoint malware because package installation often happens inside trusted build, testing and deployment environments. A poisoned dependency installed during automated CI/CD runs may gain access to secrets with broad privileges. Developer laptops may also hold long-lived tokens, cloud credentials and SSH keys, creating a path from a single package install to repository takeover or unauthorised software release.

The article PyPI attack widens developer supply-chain risk appeared first on Arabian Post.

The update, released on 8 June 2026, addresses flaws spanning memory corruption, privilege escalation, denial of service, cross-site scripting and unsafe handling of backend responses. The affected versions stretch across much of the 2.4 branch, with several vulnerabilities present from 2.4.0 through 2.4.67. The 2.4.68 build is now the recommended general availability release for the long-running 2.4. x line.

The most operationally significant fixes are in modules commonly deployed in reverse proxy, WebDAV, LDAP, TLS and HTTP/2 environments. While none of the flaws fixed in 2.4.68 has been rated critical, several are classed as moderate and could expose servers to disruption, unauthorised file access or unsafe parsing behaviour when combined with specific configurations.

One privilege management flaw affects expression handling in. htaccess across multiple modules. It could allow local. htaccess authors to read files using the privileges of the httpd user, raising concern for shared-hosting environments and platforms where delegated configuration is permitted. The issue affects Apache HTTP Server versions up to 2.4.67 and is among the most closely watched items in the patch set.

The release also fixes a denial-of-service weakness in mod_http2 that could be triggered through malicious HTTP requests. HTTP/2 support is widely enabled across high-traffic sites, APIs and content delivery environments, making the flaw important for operators managing systems that depend on persistent connections and multiplexed streams.

Several proxy-related vulnerabilities are also covered. A buffer overflow in modproxyhtml could be triggered by an untrusted backend, while ProxyPassReverseCookie handling carried a heap-based buffer overflow risk when interacting with malicious backend servers. Another flaw in modproxyftp involved an infinite-loop condition tied to attacker-controlled backend FTP servers, and a separate cross-site scripting issue affected HTML directory listing generation in modproxyftp.

The update further resolves a path-handling issue in moddavfs that could allow a WebDAV content author to manipulate trusted DAV property databases, with the potential to cause child process crashes. WebDAV is less visible than standard HTTP serving but remains in use in document management, publishing and legacy collaboration environments.

Memory-safety fixes make up a significant part of the release. These include a use-after-free condition in modldap per-directory configuration, a heap overflow in modxml2enc, an out-of-bounds read involving response header merging in modheaders and modmime, a buffer over-read in mod_ssl during outbound OCSP requests, and a heap underflow tied to crafted regular expressions in configuration.

The breadth of the fixes shows the continuing risk faced by modular web server platforms, where vulnerabilities may not affect every deployment but can become serious when enabled modules intersect with exposed services, untrusted backends, shared hosting models or complex authentication rules. Administrators are being urged to review active modules rather than assume that a vulnerability is irrelevant because the core server appears stable.

Apache remains one of the most widely deployed web servers. Current web technology surveys show it is used by roughly 23 per cent of websites whose server software is known, with the overwhelming majority of Apache deployments running version 2. x. That footprint gives even moderate-rated vulnerabilities substantial operational significance because patch delays can leave large numbers of systems exposed.

The 2.4.68 release follows Apache HTTP Server 2.4.67, issued in May, which addressed a separate HTTP/2 double-free flaw that could lead to denial of service and possible remote code execution in Apache HTTP Server 2.4.66. That earlier issue sharpened attention on HTTP/2 handling and reinforced the need for administrators to track point releases closely rather than waiting for major version changes.

Security teams are expected to focus first on servers exposed directly to the internet, reverse proxies handling untrusted upstream traffic, shared-hosting nodes, systems with. htaccess delegation, and installations using modhttp2, modproxy, moddavfs, modldap, modssl or XML conversion modules. Enterprises with layered patch approval processes may also need to check whether distribution-maintained packages have backported fixes without changing the visible upstream version number.

The article Apache update closes server security gaps appeared first on Arabian Post.

The campaign, tracked by security researchers as UNK_DeadDrop, unfolded over April and May and reached targets in technology, finance, cryptocurrency, education, business services and other sectors. More than 250 phishing emails were sent during a six-week burst, with most victims approached through developer job or project-review lures that directed them to attacker-controlled GitHub repositories.

The attackers posed as recruiters, employers or project owners seeking technical assessments. Targets were asked to clone a repository and open it in Visual Studio Code or Cursor, both widely used development environments. The malicious repositories were designed so that opening the project folder could silently trigger preconfigured tasks, reducing the need for victims to run obvious malware commands.

Once activated, the infection chain deployed platform-specific loaders for Windows, macOS and Linux. The malware installed a malicious Visual Studio Code extension disguised as a legitimate Google-related service and connected to command-and-control infrastructure. The payload then supported system reconnaissance, remote command execution and the theft of browser wallet extensions, decrypted credentials and desktop cryptocurrency wallets.

The operation shows how North Korea-aligned cyber groups are adapting to the software supply chain rather than relying only on conventional phishing attachments. Developers are attractive targets because they often hold access tokens, private repositories, cloud credentials and crypto wallets, and because technical assessments can plausibly require them to run unfamiliar code on their own machines.

The new campaign overlaps in tactics with the broader North Korea-linked “Contagious Interview” ecosystem, which has used fake job interviews and coding challenges since at least 2022 to compromise developers. Researchers have treated UNK_DeadDrop as a separate activity cluster because the latest telemetry does not show direct operational overlap, even though the tradecraft, targeting and financial motive fit the wider pattern.

Cryptocurrency remains a central focus. North Korea-linked actors stole at least $2.02bn in digital assets in 2025, pushing the estimated cumulative total to $6.75bn. The pattern has shifted towards fewer but larger compromises, with attackers increasingly pursuing privileged access inside exchanges, custodians and Web3 firms instead of relying only on direct wallet theft.

The stakes were underlined by the February 2025 Bybit breach, when attackers attributed to North Korea stole about $1.5bn in virtual assets from the Dubai-based exchange. That incident put renewed pressure on trading platforms, custodians and wallet infrastructure providers to harden signing processes, employee access controls and front-end transaction verification.

The developer-lure campaign also sits alongside a parallel North Korean IT worker threat. Skilled operatives using fabricated or stolen identities have sought remote jobs with technology companies, including crypto businesses, to generate revenue and obtain internal access. Some operations have involved laptop farms, forged credentials, compromised online profiles and facilitators who help route traffic or pass identity checks.

For companies, the risk is no longer confined to hiring fraud or endpoint compromise. A developer infected through a code-test repository could expose corporate source code, API keys, cloud credentials and production secrets. In crypto firms, the same foothold can give attackers a route toward wallet infrastructure, transaction-signing systems, smart-contract deployment tools or customer data.

The abuse of trusted developer platforms complicates detection. GitHub repositories, npm packages, Python libraries and editor extensions are part of everyday engineering work. A malicious assessment can look like a legitimate test, while the use of cross-platform tooling allows attackers to reach mixed corporate environments without tailoring each lure from scratch.

Security teams are tightening controls around recruitment workflows, including isolating coding assessments in disposable virtual machines, blocking automatic task execution in code editors, reviewing extension permissions and separating personal wallets from work devices. Companies are also expanding scrutiny of unsolicited recruiter contacts, newly created project repositories and requests to run package-installation commands outside approved build pipelines.

The article Fake coding tests expose crypto developers appeared first on Arabian Post.