registry / @hostinger/mcp / 3.10.3
@hostinger/mcp@3.10.3
MCP server for Hostinger API
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe flagged process execution is limited to explicit build or bootstrap workflows, and the OAuth code defaults to Hostinger’s auth service. The inspected sources show no install hook, unrelated credential transfer, or automatic account action.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
The MCP runs when started as a CLI or imported from its main entry; the headless bootstrap runs only when explicitly launched.
Impact
The inspected behavior supports Hostinger API access and OAuth sign-in; no unrelated credential transfer or hidden install-time action was found.
Mechanism
The bootstrap runs the Hostinger MCP through npx with fixed arguments. OAuth tokens are exchanged with the configured issuer, which defaults to auth.hostinger.com, and credentials are saved locally.
AI rationale
The flagged process execution is limited to explicit build or bootstrap workflows, and the OAuth code defaults to Hostinger’s auth service. The inspected sources show no install hook, unrelated credential transfer, or automatic account action.
Evidence
dist/~/.config/hostinger-mcp/credentials.json%APPDATA%/hostinger-mcp/credentials.json
Network endpoints1
auth.hostinger.com
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package’s main entry and CLI binaries start the Hostinger API MCP server.
- There are no install lifecycle scripts; the build script compiles TypeScript and prepares dist when explicitly run.
- The headless bootstrap invokes the published Hostinger MCP package with fixed arguments and checks for existing authentication before starting login.
- OAuth uses Hostinger’s auth service by default and sends tokens to that issuer.
- OAuth credentials are stored under the user’s hostinger-mcp configuration directory.
Evidence against
- The bootstrap uses npx with @latest, so an explicitly launched bootstrap can resolve a newer published version.
- The OAuth issuer can be overridden through OAUTH_ISSUER.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsMinifiedUrlStrings
Source & flagged code
9 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 · L18•matchType = normalized_sha256
matchedPackage = hostinger-api-mcp@3.5.0
matchedPath = build.js
matchedIdentity = npm:aG9zdGluZ2VyLWFwaS1tY3A:3.5.0
similarity = 1.000
summary = normalized source hash matched finalized malicious source
High
Known Malware Source Similarity
Source file is highly similar to a previously finalized malicious package; route for source-aware review.
build.jsView on unpkgskills/headless/connect/bootstrap.mjs
Findings
10 High3 Medium4 Low
HighChild Processbuild.js
HighShell
HighRuntime Package Installbuild.js
HighKnown Malware Source Similarityskills/headless/connect/bootstrap.mjs
HighKnown Malware Source Similaritysrc/core/oauth.js
HighKnown Malware Source Similaritysrc/core/oauth.ts
HighKnown Malware Source Similaritybuild.js
HighKnown Malware Source Similaritysrc/core/skills.js
HighKnown Malware Source Similaritysrc/core/skills.ts
HighKnown Malware Source Similarityskills/headless/steps/05-design/logo-kit.mjs
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
Affected versions and remediation
This report applies to @hostinger/mcp@3.10.3.
See all versions of @hostinger/mcp for other recorded verdicts.
- Review the evidence and your use of @hostinger/mcp@3.10.3 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.