registry / @hostinger/mcp / 3.22.3
@hostinger/mcp@3.22.3
MCP server for Hostinger API
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe flagged OAuth code implements Hostinger sign-in and token refresh, while the shell and npx references serve the build and documented connection workflow. I found no install hook or unrelated credential destination in the reviewed paths.
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 starts when invoked; browser sign-in occurs when explicitly requested or when authentication is needed for an API call. The headless bootstrap runs when invoked by its connection instructions.
Impact
The reviewed behavior supports user-directed Hostinger account access. No unrelated credential transfer or concealed execution was identified.
Mechanism
OAuth uses a loopback callback and sends authorization or refresh requests to the configured issuer. API requests use the Hostinger API base URL, configurable by the user. The bootstrap invokes this package through npx.
AI rationale
The flagged OAuth code implements Hostinger sign-in and token refresh, while the shell and npx references serve the build and documented connection workflow. I found no install hook or unrelated credential destination in the reviewed paths.
Network endpoints4
auth.hostinger.comdevelopers.hostinger.comraw.githubusercontent.comregistry.npmjs.org
Decision evidence
public snapshotAI called this Clean at 97.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package entry points expose Hostinger MCP server commands, consistent with its stated purpose.
- OAuth sign-in uses a loopback callback and exchanges an authorization code with the configured issuer.
- The runtime provides explicit --login and --logout commands; its default API host is developers.hostinger.com.
- The headless bootstrap invokes the package itself through npx as part of its documented connection flow.
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 = normalized_sha256
matchedPackage = hostinger-api-mcp@3.5.0
matchedPath = [redacted].mjs
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.
Findings
1 Critical4 High3 Medium4 Low
CriticalPrevious Version Dangerous Deltasrc/core/oauth.js
HighChild Processbuild.js
HighShell
HighRuntime Package Installbuild.js
HighKnown Malware Source Similarityskills/headless/connect/bootstrap.mjs
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @hostinger/mcp@3.22.3.
See all versions of @hostinger/mcp for other recorded verdicts.
- Review the evidence and your use of @hostinger/mcp@3.22.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.