Aroshka Cloud Faces Scrutiny Over Alleged False Claims of SOC 24/7 Operations and High-End Infrastructure
Aroshka Cloud has accused StackWorks of conducting a DDoS attack and running an OSINT campaign after the studio published the third part of its investigation into the cloud storage service.
Within hours of the third article, the provider released five blog posts alleging that StackWorks possessed direct or indirect links to coordinated technical attacks. The posts named a StackWorks employee and referenced the studio’s website while claiming the attack reached 3.5 Gbit/s and was detected by an alleged SOC 24/7 team.
StackWorks denies any involvement in attacks and has sent a pre-trial claim demanding removal of the posts and publication of a retraction. The service refused within seven minutes and published an additional post about the claim itself.
Examination of Aroshka Cloud’s own public statements and job advertisements reveals multiple contradictions. Earlier postings sought support staff to answer messages “according to ready templates” with no technical knowledge required, while later orders described a pool of five VDS servers that later expanded to requests for up to eight NVIDIA H200 GPUs, 3–6 TB RAM, and 400 Gbit/s InfiniBand connectivity.
Public DNS records show the domain resolves to a single IP address hosted by Scalaxy B.V. in Almaty, Kazakhstan, with no protective CDN headers present. The service’s claimed multi-country infrastructure and advanced security operations are not corroborated by these technical details.
Additional discrepancies include mismatched time zones between the website settings (Europe/Moscow), the dev.to profile (Amsterdam), and email headers (+04:00), as well as statistical claims that appear internally inconsistent regarding user growth and partner payouts.
The service is built on the off-the-shelf BeDrive script from Vebto, contradicting earlier marketing statements that presented it as a custom-built platform significantly cheaper than Google Drive.
Related articles
Reports Surface on Alleged De-Anonymization of Admins Running Major Russian Hacker Forums
An independent researcher has compiled publicly available information pointing to the possible identities of administrators behind prominent Russian-language darknet forums including exploit.in and duty-free.to. The analysis traces exploit.in back to its 2006 launch by a user known as Toha, later linked to Ukrainian authorities or associates, with the forum reportedly transferred or sold. Forum moderator Quake3, identified in open sources as Anatoly Kravchuk, ceased activity in October 2026 and appears on a German police wanted list. Additional details from forum posts and anonymous Telegram channels name Mikhail Rytikov, known as Abdulla, as a key figure tied to server hosting and operations. The report also notes the recent involvement of known Russian hacker wazawaka on duty-free.to and highlights the declining viability of several legacy forums due to law enforcement actions. All claims are presented as unverified public speculation without new original sourcing.
Google Strengthens Chrome Defenses Against ClickFix Clipboard-Based Scams
Google has updated Chrome to detect and warn users about malicious commands copied to the clipboard as part of ClickFix attacks. These scams trick users into pasting harmful scripts into system tools such as PowerShell under the guise of fixing errors or providing tech support. The new protections activate when Enhanced Protection in Safe Browsing is enabled and send suspicious commands for analysis after removing personal data. Google has also shifted scam page detection from a local Gemini model to a server-side implementation to improve accuracy against fake tech support, antivirus, and browser update sites. The changes make it harder for attackers to bypass browser download checks by abusing clipboard and system console execution. Official details were published in the Google Security Blog.
SPF, DKIM and DMARC: Practical Guide to Detecting Email Spoofing and Phishing
The article explains how email authentication mechanisms SPF, DKIM, and DMARC work together to combat spoofed messages that impersonate trusted services. It provides concrete DNS record examples and shows how to interpret Authentication-Results headers in received emails. SPF verifies authorized sending IP addresses but does not check the visible From address. DKIM adds cryptographic signatures to message content and headers, while DMARC ties these checks to the sender domain visible to users and defines handling policies. The guide also covers common configuration errors, forwarding issues, and why successful authentication does not guarantee message safety. It concludes that these protocols must be combined with additional security measures such as attachment scanning and user awareness training.
JPAAWG 9th General Meeting to Examine AI-Driven Messaging Threats and Global Standards in Tokyo
The Japan Anti-Abuse Working Group will hold its ninth annual General Meeting on November 5-6, 2026, in Tokyo as a hybrid event focused on evolving messaging security challenges. Keynote speaker Tom Bartel from M3AAWG will address worldwide anti-abuse trends and the practical realities of AI-powered attacks and defenses. Sessions will cover the recently standardized DMARCbis specification under RFC 9989, ongoing work on DKIM2 to counter replay attacks, BIMI logo display adoption, and sender guidelines for AI-generated email summaries. Practical workshops will teach DMARC report analysis using real sample data along with related technologies such as ARC, DNSSEC, and MTA-STS. Government agencies including the National Police Agency and Ministry of Internal Affairs and Communications will also present, alongside a dedicated track on post-quantum cryptography.