Skip to content

Conversation

@boku7
Copy link
Contributor

@boku7 boku7 commented Mar 20, 2025

VS Code Electron application hollowing with Node.JS JavaScript C2 code and arbitrary Node.JS JavaScript code execution

Copy link
Member

@wietze wietze left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @boku7 thanks for this - a few questions from me.

Created: 2025-03-20
Commands:
- Command: Code.exe
Description: Generate Node.JS JavaScript payload and package.json, and save to "%LOCALAPPDATA%\\Programs\\Microsoft VS Code\\\\resources\\app\\" before executing.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Generate Node.JS JavaScript payload and package.json

I can't find references to package.json in the blog, how does this work? Or is it the technique described in one of the blog posts you link, https://l--k.uk/2022/01/16/microsoft-teams-and-other-electron-apps-as-lolbins/ ?

Detection:
- IOC: "%LOCALAPPDATA%\\Programs\\Microsoft VS Code\\resources\\app directory created"
- IOC: "%LOCALAPPDATA%\\Programs\\Microsoft VS Code\\Code.exe file created/modified by non-Code installer/updater"
- Sigma: https://github.com/SigmaHQ/sigma/blob/43277f26fc1c81fc98fc79147b711189e901b757/rules/windows/process_creation/proc_creation_win_susp_electron_exeuction_proxy.yml
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

From the description this Sigma rule appears to be targeting other Electron applications, not including code.exe, and seemingly using a different technique than described here - is that correct?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants