Still not dynamically generating and packaging an extension with yo code <name> and vsce package, but the pre-built extension contains enough code to check in with Mythic and nothing else.

Must exit while running, or not continue execution on start, if the previously defined date/time has passed

Are you planning to update Venus for Mythic 3.0?

Need to determine the correct way to do this with setInterval() in Node.js

When an operator creates a Venus paylaod in Mythic, it gives back a pre-built VSIX file that technically works but:

1. Doesn't connect to Mythic C2
2. Doesn't contain any custom malicious code ("Hello world" is sufficient)

Essentially a VSIX file needs to go in Payload_Types/venus/agent_code/ and get read and returned during the build process.

This confirms that all of the mechanics of installing the external Payload works, as well as getting an installable VS Code extension from the build process.

Payload build process does not produce a .vsix file—it returns a zipped folder of the extension's source, which should be modified and then packaged for installation by operators with vsce package.

I plan to support both a finished .vsix and source .zip payload download in the future. ✨

Not being able to directly manipulate the values in global storage like a callback UUID makes some testing frustrating.

Memento API: https://code.visualstudio.com/api/references/vscode-api#Memento

Hey,
I'm using Mythic 2.3.7 and Venus 0.3.0 and I'm getting the following error when I try to generate a Venus payload:
"Parameter has crypto_type none, but venus has no translation_container and venus doesn't want Mythic to handle encryption"
I've tried changing some of the build and C2 parameters but I got the same error every time.

I also couldn't find any documentation regarding that error, so I would really appreciate any help or direction I can get in that matter.
I'm running my entire Mythic setup on an Ubuntu 20.04 VM.
Also worth mentioning that other Mythic payloads are installed and generated successfully (such as Merlin and Poseidon)

Thanks,
Bar

See https://docs.mythic-c2.net/v/version-2.2/updating/mythic-2.1-greater-than-2.2-updates/agents-2.1.-greater-than-2.2.2#build-status

Follow instructions in https://docs.mythic-c2.net/v/version-2.2/updating/mythic-2.1-greater-than-2.2-updates/agents-2.1.-greater-than-2.2.2

Now that there are more than a couple of commands and complexity is increasing. Place each command's source into its own file then pull into extension.js. Will need some sort of command name to function mapping.

See https://docs.mythic-c2.net/v/version-2.2/updating/mythic-2.1-greater-than-2.2-updates/agents-2.1.-greater-than-2.2.2#commandopsec

Need to sort out Node.js build environment issues first

https://code.visualstudio.com/api/working-with-extensions/bundling-extension

Minify, as well ("compacts source code by removing whitespace and comments and by changing variable and function names into something ugly but short").

Depends on #15

Currently vsce package throws a warning that you need to acknowledge

Using a .vscodeignore file

• READMEs
• Anything mentioning Mythic or only necessary for Payload building
• Unit and integration VS Code Extension test files
• etc

Depends on #15

Combining upload and run

Then refactor to cleanup any overly-simple code from the first pass at command support

Rather than return the same pre-built VSIX for every Mythic Payload created:

1. Make a new one the standard way with yo code <name>
2. Copy over or modify files in place as necessary
3. Then package it all for installation with vsce package.

Modifications

• Payload UUID
• VS Code Extension name
• VS Code Extension display name
• VS Code Extension description
• VS Code Extension publisher
• VS Code Extension repository
• VS Code Extension version
• Callback host
• Callback port
• POST Request URI
• User Agent
• Callback interval

Doesn't really matter what it does. Still not building and packaging an extension on Payload creation.

Before moving on to a C2 loop and executing commands requested by an operator, we need some way of storing state at least to keep track of the callback UUID returned by Mythic on checkin, and probably other things. I would prefer to use something built into VS Code for stealth and durability, so I've decided to go with
ExtensionContext.globalState, which is a global key/value store that persists across VS Code sessions. Docs on that:

• https://code.visualstudio.com/api/references/vscode-api#ExtensionContext.globalState
• https://code.visualstudio.com/api/references/vscode-api#Memento

HTTP C2 parameter is called query_path_name

• ls
• cat
• rm
• cd

Write to the extension's section of VS Code global storage, or an arbitrary location (with a warning?)

• process.exit() doesn't seem to work
• process.kill(process.pid, 'SIGTERM') stops the entire extension host, which pops an alert and very obviously breaks the editor:

Just stop the C2 loop and allow the extension process to stay alive?

https://code.visualstudio.com/api/extension-guides/workspace-trust

[] mythic-cli version: v0.2.22
[] Mythic Server version: v3.2.20-rc11
[*] React UI Version: v0.1.86

PRETTY_NAME="Ubuntu 24.04 LTS"
NAME="Ubuntu"
VERSION_ID="24.04"
VERSION="24.04 LTS (Noble Numbat)"

Venus is not available in the UI under Payloads\C2 Services. CLI shows it installed.
Name ContainerStatus ImageBuilt DockerComposeEntry
apollo Up 5 hours true true
dns Up 5 hours true true
nimplant Up 5 hours true true
venus Up 5 hours true true
apfell N/A false true
athena N/A false true
dynamichttp N/A false true
http N/A false true
httpx N/A false true
thanatos N/A false true

Is there a fix I'm missing? Thanks!

Using vscode.window.showInformationMessage()

• Information/Warning/Error

VS Code's Clipboard API provides read/write capability and applies to the system clipboard, so we can make this work the way Apfell's clipboard command does: https://code.visualstudio.com/api/references/vscode-api#Clipboard

Goes in documentation-payload/