NIK C2 Malware Can Use Your OpenAI API Key
Cisco Talos reported Windows malware that may exfiltrate data and call OpenAI using keys found on the victim's machine — API keys are authority criminals can steal.
Short answer
Talos described NIK C2 malware that can use a victim's stored OPENAI_API_KEY for API calls — charges and logs may appear legitimate while an attacker controls the requests. Protect keys, issue scoped limits, monitor anomalous usage, rotate credentials after compromise, and never treat a valid key alone as proof of who acted.
Imagine discovering that criminals had broken into your computer. Now imagine finding that, while stealing information, they had also used your artificial intelligence account to help them.
That is one of the unusual risks identified in a report published by cybersecurity researchers Cisco Talos on 29 October 2026.
Talos described a Windows malware framework called NIK C2, which it says it observed in the wild. The software allows an attacker to control an infected computer and carry out intrusive activities, including collecting passwords, recording keystrokes, capturing screenshots, and deploying ransomware that locks the victim's screen.
What makes the framework particularly notable is its ability to send requests to OpenAI's application programming interface. An attacker can supply a key to access the AI service. But if no key is supplied, the malware can check the compromised computer for a commonly used setting called OPENAI_API_KEY. If it finds a working key, requests can be made using the victim's credentials.
That means the AI activity could be charged to the legitimate account holder and recorded under the victim's account, even though the requests were initiated by an intruder.
Talos did not identify the affected organisations or quantify how many infections had occurred. It remains unclear how frequently attackers actually used stolen AI keys in this way. The report concerns the criminal misuse of an available API, not any suggestion that OpenAI distributed the malware.
Why this matters
AI systems increasingly use digital access keys to interact with other services. These keys often sit quietly inside software settings, development tools, or work computers, where employees rarely notice them.
If an attacker obtains a key, the resulting activity may look authorised to the service provider. Financial charges, confidential information, and investigation records can all become more complicated.
The case also shows how AI can shorten the time between stealing information and acting on it. Tools that once required several separate stages can now be connected inside one attack.
What to do
Protect AI credentials. Avoid leaving powerful, long-lasting keys in general computer settings or shared files.
Give each system limited access. Issue separate keys for different applications and provide only the permissions and spending limits needed.
Watch for unusual activity. Monitor unexpected request volumes, costs, times of use, and programs calling AI services.
Respond to compromised devices. Replace potentially exposed credentials and inspect activity from both the computer and the AI provider.
Keep reliable records. Do not assume that use of a valid key proves which person, program, or organisation made the request.
Sources
- Cisco Talos, 29 October 2026 — NIK C2 AI-enabled command-and-control framework.
- ISO/IEC 42001 explained — International Organization for Standardization.
We inventory AI services and credentials, set approval and monitoring expectations, and prepare cross-boundary incident response — through gap assessment and AIMS work.