Search This Blog

Powered by Blogger.

Blog Archive

Labels

Footer About

Footer About

Labels

Latest News

Think Hotel Wi-Fi Is Safe? Hackers Have Several Ways to Prove You Wrong

  For many travelers, connecting to hotel Wi-Fi is one of the first things they do after checking in. But while some guests use the network ...

All the recent news you need to know

ShinyHunters Data Leaks Fuel $2,000 Sextortion Email Scam

 

Cybercriminals are exploiting email addresses exposed in previous ShinyHunters data leaks to conduct a new sextortion campaign demanding $2,000 in Bitcoin. The fraudulent messages falsely claim that ShinyHunters compromised victims’ phones and computers, accessed their cameras and microphones, and recorded them visiting adult websites. However, the campaign appears to involve unrelated scammers who downloaded previously leaked information and are using it to make their threats appear credible. 

The emails reportedly use random sender addresses and names such as “ShinyHunters” or “You’ve Been HACKED.” Their subject line commonly reads “Information about your online security.” In the messages, attackers mention companies whose databases were previously exposed, including Amtrak, Hallmark, Substack, Betterment, CarGurus, ADT, Panera Bread, and McGraw Hill. By identifying a company connected to the recipient’s email address, scammers attempt to create the impression that they specifically targeted the victim. 

The scam messages claim that attackers installed malware capable of accessing a victim’s microphone, camera, keyboard, photographs, browsing history, conversations, and contact list. They then threaten to send allegedly recorded intimate videos to the recipient’s family, friends, colleagues, and business contacts unless payment is made within 48 hours. The emails also instruct recipients not to contact law enforcement, reply, or reset their devices, claiming that stolen data is stored on remote servers. These warnings are intimidation tactics rather than evidence of a genuine device compromise. 

According to the report, the campaign may have begun in April, with victims and organizations sharing similar warnings online. Betterment acknowledged that some customers received threatening emails and described them as a common extortion scam. The company emphasized that knowing someone’s email address does not give criminals the ability to install malware or access that person’s device. It advised recipients not to reply, pay, click links, or open attachments, while asking anyone who interacted with the message to contact its fraud team. 

People receiving these emails should remain calm and avoid paying the Bitcoin demand, because payment does not guarantee that scammers will stop contacting them. Recipients should preserve the message as evidence, report it to their email provider and relevant cybercrime authorities, then delete it after checking for suspicious account activity. They should also use unique passwords, enable multifactor authentication, update devices, and monitor accounts associated with the exposed email address. The campaign demonstrates how data stolen in one breach can later be reused by unrelated criminals to support convincing but false threats.

GrapheneOS Duress Feature Puts Digital Privacy and Evidence Laws to the Test

 

A federal case concerning a local Atlanta activist is fueling controversy over privacy issues relating to cell phone searches and whether simply wiping data from a device qualifies as destroying evidence. The case involves GrapheneOS, an open-source privacy-focused customized Android OS that utilizes the so-called duress PIN/password to permanently delete data from a phone if the correct code is entered by investigators. 

GrapheneOS developers describe their creation’s features on the project’s website, noting that it includes a “duress PIN/password” that causes the phone to immediately wipe all user data and any eSIMs from the device when the “wrong” passcode is entered at the time of credential prompt. According to court records, and reports by the press, in January 2025, Samuel Tunick, an Atlanta-based activist, was taken into custody by the US Customs and Border Protection (CBP) agents at the airport in Atlanta upon his return from the Dominican Republic. 

It seems Tunick was questioned by the customs officials several times and eventually gave them a password to his phone. His phone was wiped immediately after he entered the code. Samuel now faces charges brought by federal prosecutors who alleged that he “conspired to destroy property of the United States.” The defense is arguing that the search was not lawful; the activist was not informed of his constitutional rights and was not allowed to contact a lawyer. 

Additionally, Samuel’s attorney points out that Tunick was accused of possessing child sexual abuse material, and the only reason why he was searched was because of his activism surrounding the Stop Cop City movement. It is worth noting that privacy and security specialists have raised concerns regarding the matter and regard it as an important precedent. The GrapheneOS Foundation, an entity that maintains the software, has stated that it believed that its customized Android OS features “security capabilities that are appropriate and legitimate.” 

Some experts suggest that even if Tunick did wipe his phone, there is no way investigators could prove that he did not do so because of his decision to employ GrapheneOS. The case creates grounds for debate about the potential for cell phone software to create challenges for law enforcement. In particular, the case’s outcome will set a legal precedent about whether a device owner’s intentional interference with a search (by wiping data) constitutes evidence tampering. 

GrapheneOS itself is a valid privacy-centric OS, but the case concerning the Atlanta activist will shape the jurisprudence surrounding the wiping of cell phone data by users and the extent to which such action may be regarded as obstructing law enforcement.

Nearly 800 Malicious npm Packages Found Delivering Cross-Platform RAT and Infostealer


An extensive software supply chain attack targeting developers and systems running Windows, Mac OS, and Linux has identified approximately 800 malicious packages on the npm registry as part of this campaign. Researchers report that the campaign represents a shift from traditional typosquatting to high-volume "AI slop-squatting." 

A malicious attacker may generate an enormous number of plausible-looking package names rather than merely imitating a few popular libraries, which may be selected by mistake through developer typos, automated suggestions, or artificial intelligence coding assistants. The threat actors can cast a much wider net over the NPM ecosystem this way, according to OpenSourceMalware researcher Paul McCarty. The packages appear legitimate by using AI-generated, squatted, randomly generated, or typosquatted names. Upon installation, they deploy WEL1DROPPER, a downloader designed to identify the operating system and processor architecture of the victim before retrieving the appropriate malware payload. 

The README files of the packages instruct developers to load the malicious modules using JavaScript's built-in require() function, as opposed to many npm supply chain attacks that utilize preinstall or postinstall scripts. 

A malicious behavior may be less apparent during installation using this approach. Furthermore, the campaign highlights how threat actors are increasingly distributing RAT components across multiple NPM packages as opposed to relying exclusively on a single malicious package. By using this approach, malware can be spread across a broader developer ecosystem, and individual malicious components can be more difficult to detect during routine package reviews. This campaign targets developers working across Windows, Linux, and macOS environments, increasing the reach of the campaign beyond one operating system. 

When the HTTPS delivery fails, it switches to DNS TXT records associated with the domain wel1[.]ru. If the next-stage payload cannot be downloaded from Cloudflare Workers. Upon access to the compromised system, the malware retrieves multiple encoded chunks, combines them, decodes the resulting data, and executes the payload. 

Sonatype has identified the campaign as Flooding Dropper. In its analysis, Sonatype found additional capabilities designed to evade security monitoring and maintain persistence. In Windows, the malware is reported to interfere with Event Tracing for Windows (ETW) and Antimalware Scan Interface (AMSI), check for virtual environments and sandboxes, as well as establish persistence through Registry Run keys and scheduled processes. 

A compromised development environment or continuous integration/continuous delivery system can contain valuable credentials and secrets, including cloud access credentials, SSH credentials, NPM tokens, source code, and environment variables. These risks extend beyond the individual developer workstation. Infections of such systems can therefore allow attackers access to resources that go well beyond the machine originally compromised. 

As with the MacOS version, the macOS variant searches for analytical and debugging artifacts before establishing persistence with a LaunchAgent. This Linux version has been delivered as an ELF executable packed with UPX and will allow Sliver, an open-source control framework, to be deployed. Among the packages, researchers also found a legitimate file called telemetry.js. It appears, however, that the file has the same downloader functionality and is intended to create additional noise and make the packages appear to be ordinary analytics or profiling software, thus confusing. 

According to researchers, the macOS payload contains references to Russian banking and payment services, suggesting that the campaign has ties to Russian financial targets. As suspected by OpenSourceMalware, this operation could represent an evolution of the Moika campaign, which previously involved hundreds of malicious npm packages. As opposed to a conventional software vulnerability, the activity is being treated as a malware distribution campaign that has been actively deployed. Packages have been published to the public npm registry and are being removed as they become apparent. 

In addition, researchers indicated that the campaign is not related to a CVE or listed as a CISA Known Exploited Vulnerability, highlighting the primary concern as being exposed to malicious dependencies rather than exploiting a flaw in npm itself. Security teams should review dependency manifests and lockfiles for unfamiliar packages, investigate newly introduced dependencies, and monitor npm and Node.js processes to determine if there has been any unusual network activity or access to sensitive credentials. Furthermore, organizations should implement stronger controls on AI-suggested dependencies and restrict package installation through trusted internal repositories. 

As malware can execute prior to developers identifying a malicious package, finding a malicious package should result in an exposure assessment, rather than simply removing it from the system. Security risks associated with open-source software ecosystems are being increasingly highlighted by the campaign, where malicious dependencies can make trusted development environments a launching pad for broader compromises. 

Organizations should strengthen dependency monitoring, verify unfamiliar packages, and carefully inspect software introduced to developer environments and continuous integration and continuous delivery systems.

SQL Injection Used in Zero-Day Metabase Customer Data Theft Hacks


To exploit customer instances in data theft hacks, a critical Metabase SQL injection flaw was abused in zero day attacks. The vulnerability impacted Tally and Framework.

Metabase revealed the attacks last week and warned that its Metabase Cloud SaaS platform was hacked via an earlier unknown bug impacting variants 1.58 and above. Metabase warned that self-hosted deployments may also be vulnerable.

In a blogpost, Metabase CEO, Sameer Al-Sakran said that, “"We recently identified that Metabase Cloud was attacked by someone utilizing an unknown ("0-day") security vulnerability in versions 1.58 and above."

Metabase stopped the endpoints used for the attack and released a fix for the flaw. 

"The vulnerability is an unauthenticated SQL injection flaw in Metabase that can ultimately give a remote attacker administrator access to a customer's instance."

Although Metabase has not given the flaw a CVE identifier, its security advisor labels it as Critical with CVSS score of 10.0 and acknowledges that it has been actively exploited.

"This is a CRITICAL vulnerability that allows an unauthenticated remote attacker to inject arbitrary SQL into the Metabase application database, which can give them administrator access to the instance,” said a GitHub security advisory.

"From there, the attacker could change the application configuration, steal stored credentials for the connected databases, read any data accessible through those connections, and export data. Metabase has confirmed active exploitation of this vulnerability.

Metabase is available both as Metabase Cloud, the organization’s managed SaaS offering, and as software that companies can host themselves.

According to Metabase, its Cloud consumers have already been patched and upgraded while businesses running flawed self-hosted deployments should update manually.

Metabase has recommended self-hosted customers to immediately upgrade, review API keys and administrator accounts for illegal changes, remove all active user sessions, check logs and query history for any compromise, and rotate credentials for linked databases.

Companies impacted and disclosed information

Framework, a laptop maker company has confirmed data theft after hackers breached its Metabase instance. The hackers stole customer information, such as names, login IP addresses, email addresses, company names, contacts, shipping and billing addresses. 

For Framework, stolen information of Business customers may include contacts, VAT, company names, billing email address, and EIN. 

Tally also informed its users that its Metabase analytics environment was hacked on August 3.

Atlassian Rovo AI Can Be Abused to Exfiltrate Jira, Confluence Data

 




Atlassian's Rovo AI assistant has been exposed to two independent attack techniques that could cause it to retrieve Jira and Confluence data accessible to an authenticated user and transmit the information to an attacker-controlled server.

AI security firm PromptArmor and Varonis Threat Labs identified the techniques through different attack paths. Varonis' RovoBlast vulnerability has been fixed by Atlassian, while PromptArmor said its separate content-based attack remained exploitable when it published its findings on August 5, 2026.

Neither finding demonstrated a direct bypass of Jira or Confluence permissions. Instead, both attacks abused the legitimate access available to a victim's Rovo session.


Malicious content can manipulate Rovo

PromptArmor demonstrated an indirect prompt-injection attack in which attacker-controlled instructions were embedded inside content processed by Rovo.

In its example, a user uploaded a malicious document and asked Rovo to organize Jira tickets. The concealed instructions directed the assistant to search Jira and Confluence, collect information available to the user and place the results into an attacker-controlled URL request.

The attacker could then recover the stolen ticket and page contents through server logs.

PromptArmor said the victim would later see the expected ticket suggestions without an obvious indication that information had also been transmitted externally. The attack was not entirely zero-click, as the victim still had to expose Rovo to the malicious content and initiate a normal request. However, the subsequent exfiltration did not require a separate human approval step.

The firm also reported that disabling Rovo's web-search capability did not prevent its demonstrated attack because the exfiltration relied on a separate URL-retrieval capability.

PromptArmor identified the lack of a control preventing Rovo from opening a URL constructed by the model as a root cause. It also noted that Rovo can render Markdown images from model output, which could provide another potential route for data leakage, although the firm did not demonstrate a complete Rovo attack through that mechanism.

PromptArmor said it disclosed the issue to Atlassian on May 23, followed up on June 4 and July 29, and published after reporting no further communication. Its disclosure did not establish whether the content-based attack was remediated after publication.


RovoBlast used a malicious link

Varonis discovered a separate vulnerability involving Rovo's "rovoChatPrompt" URL parameter.

An attacker could place instructions directly into a specially crafted Rovo Chat link. When an authenticated user clicked the link, Rovo would load the attacker-controlled prompt and execute it using the user's existing permissions.

Varonis demonstrated the technique by instructing Rovo to retrieve sensitive information, place it into an attacker-controlled image URL and fetch the resource, thereby sending the data to the attacker.

The researchers successfully exfiltrated a private API key stored in Confluence. They also tested the technique against Jira information and data accessible through SharePoint and Outlook connectors.

The vulnerability, dubbed RovoBlast, was reported through Bugcrowd, received a P2 priority rating and earned a $6,000 bounty. Bugcrowd records Atlassian as deploying a server-side fix on July 8, 2026, after which the researcher validated the remediation and the report was marked resolved.


Enterprise permissions remain central to the risk

Rovo operates across Atlassian products and can incorporate information from connected third-party applications. Atlassian says Rovo access follows the permissions available to the user, meaning the demonstrations did not provide attackers with unrestricted tenant access.

However, the findings expose a different problem: an attacker can attempt to make the AI assistant use a victim's legitimate permissions for an unintended purpose.

Atlassian provides administrators with controls to restrict Rovo by application and, for Enterprise customers, by user group. Rovo is available on Standard, Premium and Enterprise Cloud plans, while disabling Rovo for one Jira-family application may not remove shared Rovo Search, Chat and Create capabilities if another Jira application on the same site still has Rovo enabled.

Neither disclosure reported confirmed exploitation against a real organization, and neither issue has a CVE or entry in CISA's Known Exploited Vulnerabilities catalog as of August 8.

The immediate status is therefore split: Atlassian has confirmed the RovoBlast link vulnerability is closed, while the post-publication status of PromptArmor's separate content-borne attack remains unconfirmed.

Organizations using Rovo should review which applications, user groups and third-party connectors have access, tighten underlying data permissions and avoid treating the web-search setting alone as a complete defense against AI-assisted data exfiltration.

Cloudflare Increases Annual Revenue Projection After AI Driven Traffic


Following impressive quarterly results, Cloudflare increased its full-year revenue projection above Wall Street expectations, wagering that the quick development of AI agents will continue to drive traffic throughout its network, which caused its shares to climb 18% after the bell.

More companies depending on Cloudflare

Demand for Cloudflare's cloud and security products has increased as more companies depend on its network to reliably route traffic and execute those technologies due to the rush to develop and expand AI agents.

Machines driving traffic

For the first time, machines rather than people accounted for more than half of the traffic that passed throughout Cloudflare's (NYSE: NET) network last quarter.

Following Thursday's second-quarter results, the internet infrastructure company's shares surged to a record high on Friday morning, reaching over $325 before partially reversing the day's gains.

During the results call, CEO Matthew Prince stated, "In Q2, more than 50% of the traffic flowing across Cloudflare's network was not human for the first time in human history." Months before his own prediction, which had indicated the first part of 2027, the crossover occurred.

About the growth

In light of this, Cloudflare increased its full-year revenue forecast to a range of $2.864 billion to $2.870 billion, or roughly 32% growth, and revenue increased 36% year over year to $696.1 million. Free cash flow increased 69% year over year to $56.4 million, while adjusted earnings per share came in at $0.29. Management directed revenue to increase by roughly 31% to $736 million to $737 million for the third quarter.

Additionally, there was a significant increase in customers. At the end of June, Cloudflare had 4,698 major customers, those that spend more than $100,000 annually, a 27% increase over the previous year. Additionally, current customers are spending more; dollar-based net retention, which measures how much the same customers spend after churn compared to a year ago, reached 120%, up 6 percentage points from a year ago and 2 percentage points from the first quarter.

Who pays Cloudflare?

Cloudflare is not yet paid by the machine traffic itself. Businesses who use the company's network for speed and cybersecurity pay subscriptions.

Therefore, handling a rapidly increasing amount of artificial intelligence (AI) crawler traffic primarily increases costs without increasing revenue. By that metric, Cloudflare becomes busier rather than larger in a majority-machine network.

Featured