Cisco Talos's findings on NIK C2 should worry every organization that runs an OpenAI API key on a Windows machine. According to the report published October 29, the Go-based implant can fall back on the OPENAI_API_KEY environment variable on an infected system when the operator supplies no key. That means the victim, not the attacker, may end up paying for the AI requests made from their own machine.

The billing detail is what makes this more than a clever trick. Talos said OpenAI would charge the victim's payment method, and the access logs would show the victim's key as the one making the requests. A defender reviewing those logs would see their own credentials at work and have little reason to suspect an intruder was using them to analyze stolen data.

The broader capability is also significant. Talos reported more than 52 commands covering credential theft, browser data collection, cryptocurrency wallets, Wi-Fi credentials, keylogging, screen capture and remote access. The AI client lets attackers send stolen data for analysis inside the compromised session, which Talos said erases the offline processing delays that once gave defenders time to detect intrusions.

The screen-locking ransomware module is a reminder that attackers choose the method that is fastest and least forensically visible. Talos said the module encrypted no files and left no modification timestamps or encryption markers, and that a screen lock is considerably faster to deploy than file-encrypting ransomware. Its ransom demands in Bitcoin or USDT point to a financially motivated operation.

Three steps should follow. Organizations should stop storing long-lived AI API keys in plain environment variables on endpoints, rotate existing keys, and set spending limits and usage alerts with their providers. Security teams should also treat unexpected AI API traffic from workstations as a possible indicator of compromise. Talos's assessment, made with moderate confidence, that NIK C2 is a fully functional framework rather than a proof of concept means waiting is not a sensible option.