<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Vps on IT News</title><link>https://it-news.jp/en/tags/vps/</link><description>Recent content in Vps on IT News</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>IT News</copyright><lastBuildDate>Tue, 27 Oct 2026 17:15:00 +0900</lastBuildDate><atom:link href="https://it-news.jp/en/tags/vps/index.xml" rel="self" type="application/rss+xml"/><item><title>Emergency Report: The Massive Onamae.com VPS Breach, MT4 Credential Leak, and the Threat of CORONAMNG.STORE</title><link>https://it-news.jp/en/posts/onamae-desktop-cloud-vps-breach-coronamng-store-threat-analysis/</link><pubDate>Tue, 27 Oct 2026 17:15:00 +0900</pubDate><guid>https://it-news.jp/en/posts/onamae-desktop-cloud-vps-breach-coronamng-store-threat-analysis/</guid><description>&lt;img src="https://it-news.jp/img/thumbnail/onamae-desktop-cloud-vps-breach-coronamng-store-threat-analysis-en.png" alt="Featured image of post Emergency Report: The Massive Onamae.com VPS Breach, MT4 Credential Leak, and the Threat of CORONAMNG.STORE" /&gt;&lt;p&gt;In October 2026, Japan&amp;rsquo;s largest internet infrastructure conglomerate, GMO Internet Group, suffered a catastrophic security breach targeting its flagship Windows Virtual Private Server (VPS) platform, &amp;ldquo;Onamae.com Desktop Cloud.&amp;rdquo; Following the discovery of unauthorized intrusions and malicious malware implants capable of scraping credentials, GMO took the unprecedented step on October 21 of &lt;strong&gt;forcefully suspending all 26,739 active virtual machines&lt;/strong&gt; across all subscription tiers. The crisis escalated dramatically on October 27 when threat actors surfaced a dedicated portal, &lt;strong&gt;CORONAMNG.STORE&lt;/strong&gt;, designed to publish ransom demands and showcase stolen user data. This comprehensive technical investigation dissects the incident timeline, exploitation vectors, and the critical hazards surrounding the adversary site.&lt;/p&gt;</description></item></channel></rss>