over 5,200 student records
Unit 42 has published an in-depth analysis of a threat actor, identified as BUGSTER, who is leveraging Artificial Intelligence (AI) to facilitate and execute various cybercriminal activities. The investigation reveals that BUGSTER has weaponized AI assistants, notably the Hermes Agent framework combined with the DeepSeek V4 model, by disabling safety controls to receive step-by-step guidance for attacks. The actor's campaigns, primarily focused on targets in India, include credential theft, data exfiltration, and planning for large-scale Voice over IP (VoIP) fraud. The actor successfully breached two universities, exfiltrating a MongoDB database with over 5,200 student records from one of them. This research provides a concrete example of how threat actors are operationalizing AI, using it as a force multiplier to plan and execute attacks more efficiently.
The threat actor BUGSTER demonstrates a clear methodology of integrating AI into their attack lifecycle. By using a jailbroken combination of the Hermes Agent framework and the DeepSeek V4 AI model, the actor circumvents built-in safety mechanisms to solicit advice on criminal operations. The low cost and ease of access to these tools suggest a growing trend.
The actor's activities are diverse and include:
This multi-faceted approach, powered by AI assistance, indicates a shift towards more structured and methodically planned attacks, even by potentially less-skilled actors.
BUGSTER's operations rely on a specific toolchain and a set of well-defined Tactics, Techniques, and Procedures (TTPs).
win_shell.ps1 and win_shell.bat.T1595 - Active Scanning: The actor used AI-generated reconnaissance to perform methodical enumeration of a target university's WordPress REST API.T1110.001 - Brute Force: Password Guessing: An AI-generated brute-force campaign was launched against the university website to gain access.T1078 - Valid Accounts: The goal of the brute-force attack was to acquire valid user credentials.T1530 - Data from Information Repositories: The actor exfiltrated a MongoDB database from a compromised university network.T1059.001 - Command and Scripting Interpreter: PowerShell: The actor used a win_shell.ps1 payload, indicating the use of PowerShell for execution.T1059.003 - Command and Scripting Interpreter: Windows Command Shell: The win_shell.bat payload suggests the use of the Windows Command Shell.T1583.003 - Acquire Infrastructure: Virtual Private Server: The use of Vast.ai for GPU cracking constitutes acquiring third-party infrastructure.The immediate impact of BUGSTER's activities includes the confirmed breach of two Indian universities and the theft of over 5,200 student records. This PII is highly valuable on underground forums and can be used for identity theft, targeted phishing campaigns, and other fraudulent activities. The planned VoIP fraud operation, if executed, could result in substantial financial losses for telecommunication providers. More broadly, this actor's success serves as a blueprint for other cybercriminals, demonstrating how easily accessible AI tools can be weaponized to lower the barrier to entry for complex cyberattacks, potentially leading to an increase in their frequency and success rate.
The source articles mention the following filenames used as payloads:
win_shell.ps1win_shell.batSecurity teams can hunt for related activity by searching for the following patterns:
NEXT EXPLOIT OPPORTUNITIES/wp-json/wp/v2/usersapi.deepseek.comvast.aiDefenders can take several steps to detect and respond to this type of AI-assisted threat.
Outbound Traffic Filtering (D3-OTF).Web Session Activity Analysis (D3-WSAA) is relevant here.win_shell.ps1 and monitor for command-line interpreters executing reverse shell commands. This relates to D3FEND's Process Analysis (D3-PA).To defend against attacks like those conducted by BUGSTER, organizations should implement the following controls:
Multi-factor Authentication (D3-MFA).Application Configuration Hardening (D3-ACH).Enforce MFA on all internet-facing services, especially web applications like WordPress, to prevent account takeover via brute-force.
Mapped D3FEND Techniques:
Implement strong password policies and account lockout mechanisms to make brute-force attacks more difficult.
Mapped D3FEND Techniques:
Apply egress filtering to block outbound connections to non-essential services, including AI APIs and cloud GPU providers, from servers.
Mapped D3FEND Techniques:
Use EDR solutions to monitor for anomalous process execution and script execution that deviates from normal behavior.
Mapped D3FEND Techniques:
Disable unused APIs, such as the WordPress REST API if not required, to reduce the application's attack surface.
Mapped D3FEND Techniques:
The most effective countermeasure against the credential theft portion of BUGSTER's attack chain is the enforcement of Multi-factor Authentication (MFA). This should be mandated for all user accounts, but especially for those with administrative privileges on web applications like the targeted WordPress platform. By requiring a second factor (e.g., a code from an authenticator app, a hardware token, or a biometric verification), MFA renders stolen or brute-forced passwords useless on their own. Security teams should prioritize the rollout of MFA on all internet-facing systems, including VPNs, email gateways, and administrative portals. This single control would have likely prevented the initial compromise of the university's website, stopping the entire attack chain before it could progress to data exfiltration.
To disrupt BUGSTER's operational infrastructure, organizations must implement strict outbound traffic filtering (egress filtering). The actor relied on external services like Vast.ai for password cracking and likely would use other cloud services for data exfiltration. Configure firewalls to deny all outbound traffic by default and create explicit allow rules only for known, legitimate business services. Specifically, block connections to domains associated with cloud GPU providers, public AI APIs like DeepSeek, and anonymous proxies unless there is a documented business need. This technique can prevent both the offloading of malicious computations and the exfiltration of stolen data, effectively containing a breach even if an initial compromise occurs.
Reducing the attack surface of web applications is a key preventative measure. In this case, the actor targeted the WordPress REST API for enumeration and brute-forcing. If this API is not essential for the website's functionality, it should be disabled or restricted. Security teams should conduct regular configuration reviews of all public-facing applications. This includes disabling unnecessary features, removing default accounts, and ensuring that security headers are properly implemented. For the MongoDB instance that was breached, hardening would involve ensuring it is not publicly exposed and that it requires strong authentication and is only accessible from specific application servers, not the open internet. This proactive hardening makes it significantly more difficult for attackers to find an initial foothold.
Unit 42 published its research on the threat actor 'BUGSTER' and their use of AI in cybercrime.

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.
CyberNetSec.io uses automation to assist source monitoring, deduplication, observable extraction, and structured intelligence generation. Published analysis follows human-defined editorial standards and adds defensive context including MITRE ATT&CK, D3FEND, STIX, and Sigma where applicable. Read our editorial policy.
Help others stay informed about cybersecurity threats
Every tactic, technique, and sub-technique used in this threat has been identified and mapped to the MITRE ATT&CK framework for consistent, actionable threat language.
Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.
Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.
Structured threat data is packaged as a STIX 2.1 bundle and can be visualized as an interactive graph — relationships between actors, malware, techniques, and indicators.
Sigma detection rules are derived from the threat techniques in this article and can be converted for deployment across any major SIEM or EDR platform.