Eclipse plugins, run live before you trust them.
Eclipse plugins execute inside the workbench. Extuno diffs each update and runs it in a sandbox to catch startup execution, file access, and exfiltration - static, dynamic, and AI analysis on every scan.
eclipse plugin
Every finding is backed by evidence.
Each finding names the change, why it is dangerous, and the recommended action.
Startup hook execution
A plugin registers a startup hook that runs attacker code on launch.
Workspace file harvest
An update reads source and config files and uploads them.
New bundle dependency
The update pulls an unsigned bundle from an external update site.
Startup hooks, weaponized
Extuno captures the workbench startup chain and the data leaving the host.
- + 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
- 1Launch workbench
- 2Plugin startup hook fires
- 3Scans workspace files
- 4Opens outbound socket
- 5Exfiltrates source + secrets
Scan your first Eclipse plugin free.
Your first 5 credits are free - that is 5 full scans, no card required.
Common questions
Does Extuno support Eclipse?
Yes. Extuno scans Eclipse 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 Eclipse?
Extuno acquires the published Eclipse 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 Eclipse?
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.