extuno
Catch the extension or package that turned malicious after review.
For the security and IT teams who approved an extension or a dependency once and now own every release after it. Extuno re-scans each new version, diffs it against the one before, and names what changed: a new outbound host, a widened permission, a block of code that was not there last release - with the file and line that carries it.
What a poisoned update actually looks like.
Four rows from one diff. Each names the signal, what the previous release contained, what this release changed it to, and the file and line that carries it. Nothing here is a score.
| Signal | Previous version | This version | Location |
|---|---|---|---|
| Outbound host | none | collect.acme-cdn.net | background.js:214 |
| Remote code | none | import('https://...') | service-worker.js:88 |
| Host permissions | *://*.acme.com/* | <all_urls> | manifest.json:12 |
| Content policy | script-src 'self' | + unsafe-eval | manifest.json:31 |
Five tests on every submission.
All five run on every version. The results are diffed against the previous version, scored, and reported with the evidence attached.
You reviewed one version. Extuno watches the ones after it.
Add extensions and packages to a watchlist. Extuno re-scans on every release and routes alerts to the channels your team already lives in.
- + Scheduled re-scans on each new version
- + Alert lifecycle - open, acknowledge, resolve
- + Delivery to SIEM, Slack, Teams, PagerDuty, webhooks
- 1.4.0reviewed on release
- 1.4.1no change to permissions or hosts
- 1.4.2new outbound host in background.js:214
- 1.4.3not published yet
Protect every browser in minutes.
The companion scans installed extensions, runs a server-side deep scan, and blocks malicious sites, trackers, miners, phishing, and dangerous downloads.