# Vibe-coded ransomware extension published to official VS Code Marketplace

- ID: vibe-coded-ransomware-extension-published-official-2025-11
- Reported: 2025-11-05
- Researcher: unknown
- Organization: Secure Annex
- 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/vibe-coded-ransomware-extension-published-official-2025-11/
- Entry JSON: https://openattacks.ai/api/attacks/vibe-coded-ransomware-extension-published-official-2025-11.json
- Browse title: Vibe-coded ransomware extension published to official VS Code Marketplace
- Editorial summary: An extension named susvsex, apparently written with AI assistance, packaged file encryption and exfiltration with GitHub-based C2 and passed Microsoft marketplace review.
- Evidence class (catalog annotation): Not classified
- Source-stated target environments: Not specified
- Stage hunts and conditional defenses: https://openattacks.ai/api/defenses/vibe-coded-ransomware-extension-published-official-2025-11.json

## Technique
An extension named susvsex, apparently written with AI assistance, packaged file encryption and exfiltration with GitHub-based C2 and passed Microsoft marketplace review.

## 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
- AI coding assistant used to write the malware
- [VS Code](https://github.com/microsoft/vscode) Marketplace as delivery

## Other tooling
- unknown

## Victims and sectors
Technology and AI companies

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

## Attribution
suspublisher18 / GitHub user aykhanmv

## 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://annex.security/blog/ransomvibe ; https://thehackernews.com/2025/11/vibe-coded-malicious-vs-code-extension.html

### activity: Reported activity [execution]
An extension named susvsex, apparently written with AI assistance, packaged file encryption and exfiltration with GitHub-based C2 and passed Microsoft marketplace review.
Evidence: https://annex.security/blog/ransomvibe ; https://thehackernews.com/2025/11/vibe-coded-malicious-vs-code-extension.html

### ai: AI involvement [ai]
AI coding assistant used to write the malware · VS Code Marketplace as delivery
Evidence: https://annex.security/blog/ransomvibe ; https://thehackernews.com/2025/11/vibe-coded-malicious-vs-code-extension.html

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://annex.security/blog/ransomvibe
- https://thehackernews.com/2025/11/vibe-coded-malicious-vs-code-extension.html

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