OmniVideo no seu computador: o CLI omni, o studio local e as ferramentas do pipeline.
Flagged as agent extension risk
Allowed by default with warning: install-time first-party agent extension setup was detected.
AI security review
scanned · by lpm-firewall-ai
The SessionStart hook can trigger first-party setup that modifies workspace agent permissions, so a behavior-specific warning is appropriate. The manifest has no npm lifecycle hook, and the inspected source shows no unrelated credential transfer or broad agent-control mutation.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A Claude Code session starts with the Omni plugin installed; setup runs when the user is logged in and required components are missing.
Impact
The package’s skills can run its CLI commands and read their temporary files in that workspace without repeated approval. This is a guarded, first-party extension lifecycle capability; source inspection did not establish broad agent-control hijacking or credential theft.
Mechanism
The hook invokes `omni up --hook`, which can start detached setup. Setup syncs the package’s skills and writes CLI-specific Bash and temporary-skill Read rules to workspace settings; it may also install dependencies and a local studio service.
The manifest exposes bin/omni.mjs and has no npm lifecycle script or runtime dependency on itself.
The generated Claude plugin registers a SessionStart hook that runs `omni up --hook`; when Omni is logged in and setup is incomplete, the hook can start setup in the background.
Setup syncs the package’s skills and adds their CLI permissions to workspace settings. Those rules allow this CLI’s skill and run commands and reading its temporary skill files.
The reviewed account paths read local provider state, select enabled and logged-in configured accounts, and start the selected provider’s own interactive login; the session excerpts format provider events and tool results.
The setup behavior is part of the generated first-party plugin, which is installed separately from npm. The inspected source does not establish broad agent-control changes or transfer of saved provider credentials to an unrelated recipient.
The flagged download and service code is used for Omni setup, and the updater checks login and setup conditions before starting a versioned Omni update.
Evidence against
There is no npm install hook or runtime self-dependency in package.json.
The agent permission changes are scoped to workspace settings and rules for this CLI and its temporary skill files; the source does not show a broad global agent-setting change.
Behavioral surface
SourceChild process · Crypto · Dynamic require · Environment variables · Filesystem · Network · Shell · Web socket
Supply chainHigh entropy strings · URL strings
ManifestNo license
Scanned 622 files · 3.25 MB of source
33 external domains referenced
127.0.0.1
accounts.google.com
api.cartesia.ai
api.cloudflare.com
api.elevenlabs.io
api.fish.audio
api.openai.com
api.x.ai
audiocdn.epidemicsound.com
bun.sh
developers.facebook.com
elevenlabs.io
fish.audio
fonts.googleapis.com
fonts.gstatic.com
github.com
graph.instagram.com
oauth2.googleapis.com
omni.crievo.com
open.tiktokapis.com
openrouter.ai
play.cartesia.ai
registry.npmjs.org
schemas.microsoft.com
studio.youtube.com
www.apple.com
www.epidemicsound.com
www.googleapis.com
www.instagram.com
www.tiktok.com
www.w3.org
youtu.be
youtube.com
Findings
1 critical · 8 high · 6 medium · 5 low
Where they are, most severe file first. Code opens a file's flagged lines, with their evidence, below.