Cisco Talos exposes NIK C2: Go-based Windows RAT that uses victims' OpenAI API keys and a screen-locking ransomware module
Matéria consolidada. Reúne 2 matérias que o Tifon tinha publicado separadamente sobre a mesma história. A IA reescreveu o relatório com o que as 2 fontes trouxeram em 31/10/2026 00:03; os links antigos trazem para cá.
Cisco Talos published research on October 29, 2026 on NIK C2, a Go-based 64-bit command-and-control framework and remote access tool targeting Windows systems, observed in the wild (infosecurity-magazine.com, gbhackers.com). The implant embeds a functional OpenAI client so operators can run AI prompts from the compromised host and read responses in the C2 panel. If no operator key is supplied, it falls back to the victim's OPENAI_API_KEY environment variable, so the victim pays for inference and OpenAI logs point at the victim rather than the attacker (infosecurity-magazine.com, gbhackers.com). It also includes a screen-locking ransomware module demanding Bitcoin or USDT. With at least three implant versions seen and a live server, Talos assesses with moderate confidence that NIK C2 is an operational framework rather than a proof of concept. Coverage places it in a growing pattern of LLM-enabled malware alongside MalTerminal and the x47.c botnet (gbhackers.com).
Detalhes técnicos
- Dispatcher supports more than 52 commands: browser credential, Discord token, Wi-Fi password, crypto wallet and seed-phrase theft; keylogging; screen capture, camera, audio and clipboard surveillance; hidden VNC, SOCKS5, reverse proxy and RDP for remote control and lateral movement (gbhackers.com, infosecurity-magazine.com).
- Operators choose a prompt and model in the C2 panel; the implant sends the OpenAI request from the victim machine and returns the response, collapsing collection and exploitation into one session (infosecurity-magazine.com). The
ai_generatecommand defaults to gpt-4, uses the Chat Completions endpoint and a 60-second timeout (gbhackers.com). - The
OPENAI_API_KEYfallback is described by Talos as a deliberate design choice that obscures attribution and shifts cost to the victim (infosecurity-magazine.com). - C2: TLS WebSockets on port 443 with HTTP fallback polling every 250 ms; traffic encrypted with AES-256-GCM derived from a hardcoded seed; three prioritized C2 tiers for takedown resilience (gbhackers.com).
- Live infrastructure: 87.120.196[.]120 resolving to total-sitevv[.]lol, with certificate CN "nik-panel" (gbhackers.com).
- Persistence: registry Run key SystemLock and a watchdog process (gbhackers.com).
- Defense evasion: renames itself csrss.exe, marks itself a critical process so termination triggers a BSOD, exits on debugger detection, bypasses UAC via fodhelper.exe hijack, and patches AMSI in PowerShell (gbhackers.com).
- Ransomware module: backs up the MBR, builds an HTML lock screen demanding Bitcoin and USDT, launched via mshta.exe, with a batch loop reopening it within five seconds. No files are encrypted, which avoids file-modification and encryption markers and allows much faster deployment (gbhackers.com, infosecurity-magazine.com).
- A bootkit-preparation routine checks UEFI/BIOS and Secure Boot state and writes a placeholder bootkit.bin (gbhackers.com).
Remediação
- Audit hosts for
OPENAI_API_KEYenvironment variables and avoid storing API keys in system-wide environment variables; rotate any exposed AI API keys (infosecurity-magazine.com, gbhackers.com). - Monitor OpenAI billing and access logs for anomalous usage, and hunt for unexpected outbound traffic to AI API endpoints such as api.openai.com from endpoints that should not make such calls (infosecurity-magazine.com, gbhackers.com).
- Monitor for traffic to 87.120.196[.]120 / total-sitevv[.]lol, the SystemLock Run key, and lock_start.bat / lock_screen.html in temp directories (gbhackers.com).
- ClamAV detects the threat as Win.Trojan.GoDiscorder-10060526-0 (gbhackers.com).
Linha do tempo
-
Cisco Talos uncovers NIK C2, a Go-based Windows RAT with embedded OpenAI client and 52+ commands
ler a análise desta fonte ocultar
Cisco Talos has documented NIK C2, a Go-based 64-bit Windows remote access tool that embeds a functional OpenAI client, letting operators issue prompts from the infected host and read responses in their C2 panel. The implant communicates over TLS WebSockets on port 443 with an HTTP fallback polling every 250 ms, encrypting traffic with AES-256-GCM derived from a hardcoded seed, and uses three prioritized C2 tiers for takedown resilience. A live server at 87.120.196[.]120 resolving to total-sitevv[.]lol with a certificate CN of "nik-panel" led Talos to assess with moderate confidence that this is an operational framework rather than a PoC. Notably, the
ai_generatecommand falls back to the victim's OPENAI_API_KEY environment variable, making the victim pay for inference and attributing OpenAI logs to the victim. The tool fits a growing pattern of LLM-enabled malware alongside MalTerminal and the x47.c botnet.Technical Details
- Dispatcher supports more than 52 commands: browser credential, Discord token, Wi-Fi password, crypto wallet and seed-phrase theft; keylogging, screen capture, camera, audio and clipboard surveillance; hidden VNC, SOCKS5, reverse proxy and RDP for remote control and lateral movement.
- Persistence via registry Run key (SystemLock) and a watchdog process.
- Defense evasion: renames itself csrss.exe, marks itself a critical process so termination causes a BSOD, exits on debugger detection, UAC bypass via fodhelper.exe hijack, and AMSI patching in PowerShell.
- Ransomware module backs up the MBR, builds an HTML lock screen demanding Bitcoin and USDT, launched via mshta.exe, with a batch loop reopening it within five seconds — no files are encrypted.
- A bootkit-preparation routine checks UEFI/BIOS and Secure Boot state and writes a placeholder bootkit.bin.
- Default model is gpt-4, calls go to the Chat Completions endpoint with a 60-second timeout.
Remediation
- Monitor for traffic to 87.120.196[.]120 / total-sitevv[.]lol, the SystemLock Run key, and lock_start.bat / lock_screen.html in temp directories.
- Alert on unexpected outbound connections to api.openai.com from endpoints.
- Rotate any exposed AI API keys.
- ClamAV detects the threat as Win.Trojan.GoDiscorder-10060526-0.
-
Cisco Talos uncovers NIK C2 framework that hijacks victims' OpenAI API keys for in-session AI analysis
ler a análise desta fonte ocultar
Cisco Talos published research on October 29 detailing NIK C2, a Go-based command-and-control framework observed in the wild targeting Windows systems. The implant combines remote access, credential theft, keylogging and surveillance with an integrated OpenAI client that lets operators run AI prompts directly from the compromised host. When no operator key is supplied, the malware falls back to the victim's
OPENAI_API_KEYenvironment variable, billing the AI usage to the victim and leaving OpenAI access logs pointing at the victim's key rather than the attacker. Talos also found a screen-locking ransomware module demanding Bitcoin or USDT. With at least three implant versions observed and live infrastructure, Talos assesses with moderate confidence that NIK C2 is a fully functional framework rather than a proof of concept.Technical Details
- Go-based Windows implant supporting more than 52 commands: credential theft, browser data collection, cryptocurrency wallet theft, Wi-Fi credentials, keylogging, screen capture, remote access, lateral movement and multiple defense-evasion capabilities.
- Operators select a prompt and model via the C2 panel; the implant issues the OpenAI request from the victim machine and returns the response, collapsing collection and exploitation into a single session.
- Fallback to the victim's
OPENAI_API_KEYenvironment variable is described by Talos as a deliberate design choice that obscures attribution and shifts cost to the victim. - The ransomware module only locks the screen and encrypts no files, avoiding file-modification timestamps or encryption markers and deploying far faster than file-encrypting ransomware.
Remediation
Audit hosts for
OPENAI_API_KEYenvironment variables and avoid storing API keys in system-wide environment variables; monitor OpenAI billing and access logs for anomalous usage; hunt for unexpected outbound traffic to AI API endpoints from endpoints that should not make such calls.