registry / @hostinger/mcp / 3.12.0
@hostinger/mcp@3.12.0
MCP server for Hostinger API
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe manifest declares no install lifecycle scripts, and the runtime entry points start the Hostinger MCP server. The flagged process execution belongs to an explicit build or separately run sign-in helper, while inspected OAuth requests use Hostinger’s issuer.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review; previous stored version diff introduced dangerous source
Trigger
Starting the MCP server, using a Hostinger API tool, or explicitly running the build or headless sign-in helper.
Impact
No unrelated credential transfer, hidden install-time action, or attack behavior was identified in the inspected source.
Mechanism
The server exposes Hostinger API tools; OAuth uses the Hostinger issuer and saves credentials to the Hostinger MCP config directory. The build script invokes TypeScript compilation.
AI rationale
The manifest declares no install lifecycle scripts, and the runtime entry points start the Hostinger MCP server. The flagged process execution belongs to an explicit build or separately run sign-in helper, while inspected OAuth requests use Hostinger’s issuer.
Evidence
~/.config/hostinger-mcp/credentials.json%APPDATA%/hostinger-mcp/credentials.jsondist/
Network endpoints4
auth.hostinger.comdevelopers.hostinger.comraw.githubusercontent.comcodeload.github.com
Decision evidence
public snapshotAI called this Clean at 92.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest has no lifecycle scripts; the main entry and binaries start the Hostinger MCP server.
- The flagged build command runs the TypeScript compiler when explicitly invoked and copies package build files.
- OAuth sends authorization and refresh token requests to the Hostinger issuer and stores credentials in the user’s Hostinger MCP config directory.
Evidence against
- The headless helper uses npx to resolve @hostinger/mcp@latest when a user runs the separately documented sign-in flow.
- OAuth credential access and storage are sensitive capabilities, though the inspected flow uses them for Hostinger sign-in.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsMinifiedUrlStrings
Source & flagged code
7 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
1 Critical7 High3 Medium4 Low
CriticalPrevious Version Dangerous Deltasrc/core/skills.js
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
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
Affected versions and remediation
This report applies to @hostinger/mcp@3.12.0.
See all versions of @hostinger/mcp for other recorded verdicts.
- Review the evidence and your use of @hostinger/mcp@3.12.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.