registry / @seoagent-official/seoagent / 1.107.2

@seoagent-official/seoagent@1.107.2

The persistent AI SEO agent for Claude Code. Audits, keyword strategy, briefs, articles, real product screenshots from your repo, and the autopilot loop (cloud detects → CLI executes → ack closes) — other SEO tools write the prompt, SEOAgent runs it.

AI Security Review

scanned 28d ago · by lpm-firewall-ai

Source inspection found a CLI package with no npm install lifecycle trigger. Its Claude settings integration is tied to explicit project initialization, and the inspected source does not establish a concrete attack surface.

Static reason

High-risk behavior combination matched malicious policy.

Trigger

Explicit invocation of the `seoagent init` command.

Impact

The reviewed setup changes agent configuration as part of the requested initialization; no malicious effect was established.

Mechanism

The command initializes project files and installs a skill; its settings writer adds SEOAgent hooks to Claude settings.

AI rationale

Evidence

package.jsonindex.js

Decision evidence

public snapshot

AI called this Clean at 84.0% confidence as Benign with low false-positive risk.

Evidence for AI clean decision

package.json exposes a CLI entrypoint and declares no install lifecycle hook.
index.js names SEOAgent skill and Claude settings locations; this alone does not establish a configuration write.
The settings hook writer is reached through the explicit `init` command, which initializes the SEOAgent project and installs its skill.
The hook writer updates SEOAgent PostToolUse and SessionStart hooks in Claude settings.

Evidence against

The inspected source shows no automatic npm install trigger for the agent setup.
The agent setup is package-owned and user-invoked through `seoagent init`; no concrete malicious behavior was identified.

Behavioral surface

Source

ChildProcessEnvironmentVarsNetworkShell

Supply chain

HighEntropyStringsUrlStrings

ManifestNo manifest risk signals triggered.

scanned 1 file(s), 366 KB of source, external domains: 127.0.0.1, api.openai.com, api.replicate.com, console.anthropic.com, example.com, fal.run, registry.npmjs.org, seoagent.com, www.google.com

Source & flagged code

6 flagged

index.jsView file

87- Bundle scaffolded. L88: `,"utf-8"),r.push("log.md")),{created:r,okfDir:n}}import{log as Tt}from"@clack/prompts";var u={info:e=>Tt.info(e),warn:e=>Tt.warn(e),error:e=>Tt.error(e),success:e=>Tt.success(e),s... L89: `,"utf-8"),n}catch{return null}}var pg=1500,fg=900*1e3,Ja="Login timed out. If the browser page shows a `seoagent login --code \u2026` line, run that here; otherwise run `seoagent ... L90: `))}function Og(){return`The setup code did not bind this project. Do not continue without a successful login \u2014 get a fresh code at seoagent.com/grok, then run \`${m("login")}...

Critical

Same File Env Network Execution

A single source file combines environment access, network access, and code or shell execution with blocking evidence.

index.jsView on unpkg · L87

87Trigger-reachable chain: manifest.main -> index.js L87: - Bundle scaffolded. L88: `,"utf-8"),r.push("log.md")),{created:r,okfDir:n}}import{log as Tt}from"@clack/prompts";var u={info:e=>Tt.info(e),warn:e=>Tt.warn(e),error:e=>Tt.error(e),success:e=>Tt.success(e),s... L89: `,"utf-8"),n}catch{return null}}var pg=1500,fg=900*1e3,Ja="Login timed out. If the browser page shows a `seoagent login --code \u2026` line, run that here; otherwise run `seoagent ... L90: `))}function Og(){return`The setup code did not bind this project. Do not continue without a successful login \u2014 get a fresh code at seoagent.com/grok, then run \`${m("login")}...

Critical

Trigger Reachable Dangerous Capability

A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.

Findings

2 Critical4 High3 Medium3 Low

CriticalSame File Env Network Executionindex.js

CriticalTrigger Reachable Dangerous Capabilityindex.js

HighChild Processindex.js

HighShell

HighCommand Output Exfiltrationindex.js

HighTrigger Reachable Command Output Exfiltrationindex.js

MediumNetwork

MediumEnvironment Vars

MediumStructural Risk Force Deep Review

LowHigh Entropy Strings

LowUrl Strings

LowSuspicious Lifecycle Evidencepackage.json

Affected versions and remediation

This report applies to @seoagent-official/seoagent@1.107.2.

See all versions of @seoagent-official/seoagent for other recorded verdicts.

Review the evidence and your use of @seoagent-official/seoagent@1.107.2 before allowing it. Restrict the permissions described in this report.
Choose an independently verified alternative or release. This report does not establish that other versions are safe.

Evidence last updated: 2026-10-07 21:04:52.749Z (UTC).

Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.

registry / @seoagent-official/seoagent / 1.107.2

@seoagent-official/seoagent@1.107.2

AI Security Review

scanned 28d ago · by lpm-firewall-ai

Static reason

High-risk behavior combination matched malicious policy.

Trigger

Explicit invocation of the `seoagent init` command.

Impact

The reviewed setup changes agent configuration as part of the requested initialization; no malicious effect was established.

Mechanism

The command initializes project files and installs a skill; its settings writer adds SEOAgent hooks to Claude settings.

AI rationale

Evidence

package.jsonindex.js

Decision evidence

public snapshot

AI called this Clean at 84.0% confidence as Benign with low false-positive risk.

Evidence for AI clean decision

package.json exposes a CLI entrypoint and declares no install lifecycle hook.
index.js names SEOAgent skill and Claude settings locations; this alone does not establish a configuration write.
The settings hook writer is reached through the explicit `init` command, which initializes the SEOAgent project and installs its skill.
The hook writer updates SEOAgent PostToolUse and SessionStart hooks in Claude settings.

Evidence against

The inspected source shows no automatic npm install trigger for the agent setup.
The agent setup is package-owned and user-invoked through `seoagent init`; no concrete malicious behavior was identified.

Behavioral surface

Source

ChildProcessEnvironmentVarsNetworkShell

Supply chain

HighEntropyStringsUrlStrings

ManifestNo manifest risk signals triggered.

scanned 1 file(s), 366 KB of source, external domains: 127.0.0.1, api.openai.com, api.replicate.com, console.anthropic.com, example.com, fal.run, registry.npmjs.org, seoagent.com, www.google.com

Source & flagged code

6 flagged

index.jsView file

Critical

Same File Env Network Execution

A single source file combines environment access, network access, and code or shell execution with blocking evidence.

index.jsView on unpkg · L87

Critical

Trigger Reachable Dangerous Capability

A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.

Findings

2 Critical4 High3 Medium3 Low

CriticalSame File Env Network Executionindex.js

CriticalTrigger Reachable Dangerous Capabilityindex.js

HighChild Processindex.js

HighShell

HighCommand Output Exfiltrationindex.js

HighTrigger Reachable Command Output Exfiltrationindex.js

MediumNetwork

MediumEnvironment Vars

MediumStructural Risk Force Deep Review

LowHigh Entropy Strings

LowUrl Strings

LowSuspicious Lifecycle Evidencepackage.json

Affected versions and remediation

This report applies to @seoagent-official/seoagent@1.107.2.

See all versions of @seoagent-official/seoagent for other recorded verdicts.

Review the evidence and your use of @seoagent-official/seoagent@1.107.2 before allowing it. Restrict the permissions described in this report.
Choose an independently verified alternative or release. This report does not establish that other versions are safe.

Evidence last updated: 2026-10-07 21:04:52.749Z (UTC).

Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.