# IBM X-Force: Interlock operator Hive0163 deploys likely LLM-written Slopoly PowerShell backdoor

- ID: ibm-x-force-interlock-operator-hive0163-2026-03
- Reported: 2026-03-12
- Researcher: unknown
- Organization: IBM X-Force
- AI role: llm_generated_malware (LLM-generated malware)
- Confidence in AI involvement: not assessed
- Research / borderline: false
- Last reviewed: not assessed
- Entry page: https://openattacks.ai/attacks/ibm-x-force-interlock-operator-hive0163-2026-03/
- Entry JSON: https://openattacks.ai/api/attacks/ibm-x-force-interlock-operator-hive0163-2026-03.json
- Browse title: IBM X-Force: Interlock operator Hive0163 deploys likely LLM-written Slopoly PowerShell backdoor
- Editorial summary: A ransomware crew used a likely AI-generated PowerShell C2 client to hold a server for over a week before deploying Interlock.
- Evidence class (catalog annotation): Not classified
- Source-stated target environments: Not specified
- Stage hunts and conditional defenses: https://openattacks.ai/api/defenses/ibm-x-force-interlock-operator-hive0163-2026-03.json

## Technique
A ransomware crew used a likely AI-generated PowerShell C2 client to hold a server for over a week before deploying Interlock.

## Stack relevance (editorial)
Assessment: not\_assessed. No reviewed applicability annotation is available. Product mentions do not establish victim conditions.
A product mention alone is not a victim-side applicability mapping. Selection does not verify affected versions, permissions or compromise.

## Initial access
unknown

## AI tooling and models
- Unidentified LLM used to write malware

## Other tooling
- unknown

## Victims and sectors
Multiple sectors

## Target geography
- unknown
Target geography was not captured by the Notion feed. Actor attribution is not used as a victim location.

## Attribution
Hive0163 (Interlock ransomware)

## Scale and metrics
unknown

## Attack flow
Summary diagram derived from entry fields; a detailed sequence has not been supplied.
### entry: Reported initial access [unknown]
unknown
Evidence: https://www.ibm.com/think/x-force/slopoly-start-ai-enhanced-ransomware-attacks ; https://www.bleepingcomputer.com/news/security/ai-generated-slopoly-malware-used-in-interlock-ransomware-attack/ ; https://www.scworld.com/brief/ai-generated-malware-slopoly-used-in-interlock-ransomware-attacks

### activity: Reported activity [execution]
A ransomware crew used a likely AI-generated PowerShell C2 client to hold a server for over a week before deploying Interlock.
Evidence: https://www.ibm.com/think/x-force/slopoly-start-ai-enhanced-ransomware-attacks ; https://www.bleepingcomputer.com/news/security/ai-generated-slopoly-malware-used-in-interlock-ransomware-attack/ ; https://www.scworld.com/brief/ai-generated-malware-slopoly-used-in-interlock-ransomware-attacks

### ai: AI involvement [ai]
Unidentified LLM used to write malware
Evidence: https://www.ibm.com/think/x-force/slopoly-start-ai-enhanced-ransomware-attacks ; https://www.bleepingcomputer.com/news/security/ai-generated-slopoly-malware-used-in-interlock-ransomware-attack/ ; https://www.scworld.com/brief/ai-generated-malware-slopoly-used-in-interlock-ransomware-attacks

Connections:
- entry -> activity
- ai -> activity (AI context)

## Stage defense and hunting recommendations
Editorial recommendations, not validated coverage. Source-controlled query starters are drafts. Custom-schema examples require telemetry collection and field mapping; absence of a mapping means not assessed. MagicSword policy opportunities require managed Windows scope and enforcement.
### entry: Stage hunt not mapped yet
- Visibility: Not assessed
- Query origin: catalog_authored; status: not_assessed; log scope: gap
- Hunt hypothesis: A stage-specific hunt has not been reviewed for this part of the source account.
- Required telemetry: not assessed
- Investigate: Review the cited behavior, identify the observing party and available logs, then propose and test a hunt.
- Limitation: An unmapped stage does not mean it is undetectable or that no behavior occurred. It means this catalog has not supplied a reviewed hunt for it.
- No direct MagicSword prevention claim is recorded for this stage.

### activity: Stage hunt not mapped yet
- Visibility: Not assessed
- Query origin: catalog_authored; status: not_assessed; log scope: gap
- Hunt hypothesis: A stage-specific hunt has not been reviewed for this part of the source account.
- Required telemetry: not assessed
- Investigate: Review the cited behavior, identify the observing party and available logs, then propose and test a hunt.
- Limitation: An unmapped stage does not mean it is undetectable or that no behavior occurred. It means this catalog has not supplied a reviewed hunt for it.
- No direct MagicSword prevention claim is recorded for this stage.

### ai: Stage hunt not mapped yet
- Visibility: Not assessed
- Query origin: catalog_authored; status: not_assessed; log scope: gap
- Hunt hypothesis: A stage-specific hunt has not been reviewed for this part of the source account.
- Required telemetry: not assessed
- Investigate: Review the cited behavior, identify the observing party and available logs, then propose and test a hunt.
- Limitation: An unmapped stage does not mean it is undetectable or that no behavior occurred. It means this catalog has not supplied a reviewed hunt for it.
- No direct MagicSword prevention claim is recorded for this stage.


## MITRE ATLAS
Mappings are catalog annotations based on described behavior, not assignments or endorsements by MITRE.
No source-backed mapping is currently recorded.

## Defensive notes
unknown

## Sources
- https://www.ibm.com/think/x-force/slopoly-start-ai-enhanced-ransomware-attacks
- https://www.bleepingcomputer.com/news/security/ai-generated-slopoly-malware-used-in-interlock-ransomware-attack/
- https://www.scworld.com/brief/ai-generated-malware-slopoly-used-in-interlock-ransomware-attacks

## Source notes
Imported from the AI Threat Watch Notion feed (an automated daily scan); not yet editorially reviewed. Feed severity: Medium. Feed novelty: Evolution.
