registry / @hostinger/mcp / 3.10.0
@hostinger/mcp@3.10.0
MCP server for Hostinger API
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe manifest has no install hook, and the inspected authentication flow targets Hostinger and a local callback. Scanner similarity and network indicators alone did not establish malicious behavior.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
A user starts the MCP server or invokes its sign-in flow or tools.
Impact
No unauthorized credential transfer or other concrete attack behavior was established.
Mechanism
The sign-in flow directs the user to Hostinger authorization, receives the callback on localhost, stores tokens, and uses bearer authentication for API requests.
AI rationale
The manifest has no install hook, and the inspected authentication flow targets Hostinger and a local callback. Scanner similarity and network indicators alone did not establish malicious behavior.
Evidence
src/core/oauth.js
Network endpoints2
auth.hostinger.comHostinger API
Decision evidence
public snapshotAI called this Clean at 88.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json has no install lifecycle hook and points to the package’s MCP server entrypoint.
- OAuth uses Hostinger’s issuer, a browser authorization flow, a localhost callback, and stored credentials; runtime bearer tokens are sent to the Hostinger API.
- The flagged build and headless files implement compilation, user-facing sign-in, and logo generation; inspected behavior did not establish an attack.
- The cited Axios excerpts implement cancellation and request transport behavior, and the SDK/CORS files are dependency entrypoints or manifests.
Evidence against
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.0.
See all versions of @hostinger/mcp for other recorded verdicts.
- Review the evidence and your use of @hostinger/mcp@3.10.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.