registry / @hostinger/mcp / 3.4.0
@hostinger/mcp@3.4.0
MCP server for Hostinger API
AI Security Review
scanned 16d ago · by lpm-firewall-aiSource inspection found no install hook or concrete attack behavior. The flagged build command compiles the package, while the bundled agent setup is exposed as a resource and requires explicit use, with persistent registration described as optional.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A user launches the MCP server or explicitly runs the bundled connection bootstrap.
Impact
The inspected behavior supports user-requested Hostinger access and does not establish credential disclosure, unconsented agent configuration changes, or other attack behavior.
Mechanism
The bootstrap resolves the Hostinger MCP package through npx, reuses saved authentication when available, or starts an interactive login; agent registration is described as optional.
AI rationale
Source inspection found no install hook or concrete attack behavior. The flagged build command compiles the package, while the bundled agent setup is exposed as a resource and requires explicit use, with persistent registration described as optional.
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json defines runtime entrypoints and ordinary start, build, and TypeScript scripts; it has no install lifecycle hook.
- build.js compiles TypeScript and copies package files into dist.
- The server exposes bundled skills as readable MCP resources, and src/core/skills.js and src/core/skills.ts describe Cursor registration as optional.
- The headless bootstrap runs only when invoked; it uses npx for @hostinger/mcp and otherwise reuses existing credentials or starts an interactive Hostinger login.
- The generated API tools describe user-requested Hostinger operations, including deployment, with destructive actions identified.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsMinifiedUrlStrings
Source & flagged code
4 flaggedbuild.jsView file
2L3: import { exec } from 'child_process';
L4: import fs from 'fs';
High
18console.log('Compiling TypeScript...');
L19: exec('npx tsc', (error, stdout, stderr) => {
L20: if (error) {
High
Runtime Package Install
Package source invokes a package manager install command at runtime.
build.jsView on unpkg · L18skills/headless/connect/bootstrap.mjsView file
•matchType = previous_version_dangerous_delta
matchedPackage = @hostinger/mcp@3.2.2
matchedIdentity = npm:QGhvc3Rpbmdlci9tY3A:3.2.2
similarity = 0.879
summary = stored previous version shares package body but lacks this dangerous source file
Critical
Previous Version Dangerous Delta
This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
Findings
1 Critical3 High3 Medium5 Low
CriticalPrevious Version Dangerous Deltaskills/headless/connect/bootstrap.mjs
HighChild Processbuild.js
HighShell
HighRuntime Package Installbuild.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowSuspicious Lifecycle Evidencepackage.json
Affected versions and remediation
This report applies to @hostinger/mcp@3.4.0.
See all versions of @hostinger/mcp for other recorded verdicts.
- Review the evidence and your use of @hostinger/mcp@3.4.0 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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.