Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →cyberstrikeus/T1219.001_ide-tunneling
Adversaries may abuse Integrated Development Environment (IDE) software with remote development features to establish an interactive command and control channel on target systems within a network.
Passed 18 of 23 test cases with the skill, and 13 of 23 without it.
and 5 more in the full report
6 fixed12 passed either way4 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
A vulnerability management team is filing a security ticket for exposed developer tunneling channels that allow remote interactive sessions into internal networks without endpoint-level perimeter validation. Provide the precise Common Weakness Enumeration (CWE) identifier and title appropriate for this architectural flaw.
| Checked | Without skill | With skill |
|---|---|---|
| The response identifies the vulnerability using CWE-300. | Missed | Passed |
| The response provides the title Channel Accessible by Non-Endpoint for CWE-300. | Missed | Passed |
The instructions your model reads when the skill loads.
Sub-technique of: T1219
Adversaries may abuse Integrated Development Environment (IDE) software with remote development features to establish an interactive command and control channel on target systems within a network. IDE tunneling combines SSH, port forwarding, file sharing, and debugging into a single secure connection, letting developers work on remote systems as if they were local. Unlike SSH and port forwarding, IDE tunneling encapsulates an entire session and may use proprietary tunneling protocols alongside SSH, allowing adversaries to blend in with legitimate development workflows. Some IDEs, like Visual Studio Code, also provide CLI tools (e.g., code tunnel) that adversaries may use to programmatically establish tunnels and generate web-accessible URLs for remote access. These tunnels can be authenticated through accounts such as GitHub, enabling the adversary to control the compromised system via a legitimate developer portal.
Additionally, adversaries may use IDE tunneling for persistence. Some IDEs, such as Visual Studio Code and JetBrains, support automatic reconnection. Adversaries may configure the IDE to auto-launch at startup, re-establishing the tunnel upon execution. Compromised developer machines may also be exploited as jump hosts to move further into the network.
IDE tunneling tools may be built-in or installed as IDE Extensions.
Platforms: Linux, macOS, Windows
Identify Attack Surface: Determine if the target environment is susceptible to IDE Tunneling by examining the target platforms (Linux, macOS, Windows).
Assess Existing Defenses: Review whether mitigations for T1219.001 are in place. If defenses are absent or misconfigured, this technique may be exploitable.
Execute Test: Use tools and methods described in the MITRE ATT&CK page and external references below.
Note: No Atomic Red Team tests available for this technique. See Atomic Red Team GitHub for updates.
test cases passed, vs 13 / 23 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.