JetBrains plugins, inspected for IDE-level abuse.
JetBrains plugins can run arbitrary code in the IDE. Extuno diffs each update and runs it live to catch project-open execution, credential access, and exfiltration - with static, dynamic, and AI analysis.
jetbrains plugin
Every finding is backed by evidence.
Each finding names the change, why it is dangerous, and the recommended action.
Project-open execution
A plugin runs code the moment a project is opened, no action required.
SSH key access
An update reads ~/.ssh and posts key material off-host.
New network calls
The plugin contacts a host it never reached in prior releases.
IDE access, used against you
Extuno records the plugin's runtime behavior from startup to the first outbound beacon.
- + Vulnerability and secret-leak testing on every version
- + Static analysis reads the code without running it
- + Dynamic sandbox runs it live and records behavior
- + AI code analysis reads the full source and correlates the change against prior versions
- 1Open project
- 2Plugin loads at startup
- 3Reads ~/.ssh + env
- 4Spawns background process
- 5Exfiltrates key material
Scan your first JetBrains plugin free.
Your first 5 credits are free - that is 5 full scans, no card required.
Common questions
Does Extuno support JetBrains?
Yes. Extuno scans JetBrains with static analysis, a dynamic sandbox, and AI code analysis, and diffs every version to catch one that was clean but poisoned through an update.
How does Extuno scan JetBrains?
Extuno acquires the published JetBrains artifact, reads it statically with 1100+ rules, runs it in a network-segmented sandbox, reviews the source with AI, and diffs it against the prior version - naming the file, the change, why it is dangerous, and the fix.
What does Extuno catch in JetBrains?
Leaked secrets, obfuscated or malicious code, dangerous permissions and APIs, exfiltration and command-and-control behavior, and the headline signal: a version that turns malicious after an update.