A stealthy Windows backdoor has resurfaced alongside Daxin, a sophisticated espionage tool previously tied to China-linked activity. <\/p>\n
The newly documented implant lets an intruder type a special username at the Windows sign-in screen and, in some cases, immediately open a command shell with the system\u2019s highest privileges.<\/a><\/p>\n The activity was discovered on a compromised computer at a Taiwan-based subsidiary of a multinational high-tech manufacturer. <\/p>\n Investigators believe the initial foothold may have come through an outdated Digiwin single sign-on portal that still used Java Development Kit versions released between 2009 and 2011. Its target has strategic value to China.<\/a><\/p>\n Researchers from Symantec identified Daxin and the previously unknown Backdoor.Stupig on the same host during an investigation in May 2026. <\/p>\n Symantec said in a report<\/a> shared with Cyber Security News (CSN) that the combination suggests a long-running operation, though a direct code-level link between the two tools has not been confirmed.<\/a><\/p>\n The case matters because the backdoor operates before a normal user session begins, where many organisations have limited visibility. <\/p>\n Its design can give an attacker command execution as SYSTEM, Windows\u2019 most powerful local account, while also creating an opportunity to intercept credentials entered during the sign-in process. <\/p>\n Since it is loaded by a trusted Windows component, routine endpoint checks may not immediately distinguish it from legitimate keyboard support.<\/a><\/p>\n Backdoor.Stupig disguises itself as part of Windows keyboard support rather than behaving like a conventional remote-access program. <\/p>\n It registers as a keyboard-layout provider, causing Windows to load the malicious DLL<\/a> into winlogon.exe during startup, while returning normal keyboard data so the device appears to work as expected.<\/a><\/p>\n Once active, the backdoor watches the logon screen for usernames beginning with\u00a0 If the attacker enters only that prefix, it launches a SYSTEM command prompt on the secure desktop; if text follows the prefix, that text is executed as a command with the same level of access.<\/a><\/p>\n The program then passes the request to the legitimate Windows logon process<\/a>, which produces an ordinary failed-sign-in response. <\/p>\n This means defenders may see an unusual failed username but no obvious logon audit anomaly showing that a privileged shell was created, making a simple screen-level test unusually valuable to an intruder with console access.<\/a><\/p>\n Stupig also places hooks in Windows functions used during authentication and credential handling, allowing it to capture information inside winlogon.exe. <\/p>\n Investigators found a reference to a companion file named\u00a0 The researchers said Stupig does not match a known malware family in their similarity analysis, underscoring the value of checking unfamiliar authentication-time modules.<\/a><\/p>\n Daxin is a kernel-level Windows backdoor first exposed in 2022, although samples date to 2013. <\/p>\n Rather than making a clear outbound connection to a control server, it monitors inbound TCP traffic<\/a> for specific patterns and takes over legitimate connections to carry encrypted instructions.<\/a><\/p>\n That approach can blend malicious traffic into normal network activity and makes conventional monitoring less effective. <\/p>\n Daxin can also relay commands through multiple compromised devices, potentially giving operators a route into isolated network areas that have no direct internet connection.<\/a><\/p>\n Both samples carried early-2013 compilation timestamps, while the affected system did not begin supplying telemetry until May 12, 2026. <\/p>\n That gap, together with the group\u2019s history of quiet persistence, leaves open the possibility that the intrusion remained hidden for years and perhaps longer than a decade. <\/p>\n The malware files were also detected<\/a> under different names, a change that appeared to follow the first detection event.<\/a><\/p>\n Defenders should urgently replace unsupported Java installations and review exposed single sign-on systems, especially older Digiwin deployments. <\/p>\n They should also examine keyboard-layout registrations and DLLs loaded by winlogon.exe, investigate failed logons using unusual\u00a0 Reviewing systems that lack historical telemetry is equally important, since dormant implants may only surface when monitoring improves. This includes validating all remaining legacy assets.<\/p>\n Indicators of compromise (IoCs):-<\/strong><\/a><\/p>\nHackers Can Type a Secret Username at the Windows Login Screen<\/strong><\/h2>\n
stupig<\/code>. <\/p>\n![\"Attack](\"https:\/\/i0.wp.com\/blogger.googleusercontent.com\/img\/b\/R29vZ2xl\/AVvXsEiePYlEr24x8_Jd6DnnrGf9JuHpYfgaIMVbR9zfZf3QDuVQ8dIv_h-7cU72GnvxCiMk0DRO4OZH2TZ5_hzmabBA7YSn_M7jMpNdLaZhWTdhmv1mv0OgTAMbnNrxg1KGjZj0AReAzfRYMdhoYZimgvlJzDoQMTQsQRWbgsIeni9phIts-_sAKKuYF18kieE\/s1600\/Attack%2520chain%2520%28Source%2520-%2520Symantec%29.webp?ssl=1\")
msyun.dll<\/code>, but that payload was not among the artifacts recovered from the affected environment. <\/p>\nDaxin Signals Enduring Espionage<\/strong><\/h2>\n
stupig<\/code>-prefixed names, and hunt for the indicators below across Windows systems. <\/p>\n