registry / @hostinger/mcp / 3.19.1
@hostinger/mcp@3.19.1
MCP server for Hostinger API
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe flagged process execution is the declared build step invoking the TypeScript compiler, and the package entry starts the advertised Hostinger API MCP server. Reviewed authentication traffic goes to Hostinger services; no install hook or unrelated credential destination was found.
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
The server runs when invoked; OAuth requests occur when the user signs in or an API call needs a token.
Impact
No malicious collection, unrelated credential transfer, or unrequested account action was identified in the reviewed paths.
Mechanism
The build script invokes the TypeScript compiler. The server exposes Hostinger API tools and uses Hostinger OAuth for authentication.
AI rationale
The flagged process execution is the declared build step invoking the TypeScript compiler, and the package entry starts the advertised Hostinger API MCP server. Reviewed authentication traffic goes to Hostinger services; no install hook or unrelated credential destination was found.
Network endpoints2
auth.hostinger.comdevelopers.hostinger.com
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package declares a Hostinger API MCP server as its main entry point and exposes server commands.
- The flagged build command runs `npx tsc` and copies package files into `dist`.
- The main entry starts the MCP server with its tools, instructions, and embedded skills.
- OAuth uses Hostinger’s auth service; the API base URL is Hostinger’s developer API unless the user configures another URL.
Evidence against
- No install lifecycle scripts are declared.
- The bootstrap invokes the package’s own MCP command through npx when that bootstrap runs.
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.19.1.
See all versions of @hostinger/mcp for other recorded verdicts.
- Review the evidence and your use of @hostinger/mcp@3.19.1 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.