registry / @hostinger/mcp / 3.20.3
@hostinger/mcp@3.20.3
MCP server for Hostinger API
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe flagged process execution is a build-time TypeScript compilation step, while the OAuth code uses Hostinger's auth service and stores credentials locally. The inspected entry points and request flow show no unrelated credential collection, transmission, or automatic account actions.
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
OAuth runs when the user requests login or an API operation needs authentication; build commands run when explicitly invoked.
Impact
Normal use can access Hostinger account operations allowed by the supplied token and requested MCP tools.
Mechanism
The package authenticates with Hostinger, stores OAuth credentials locally, and uses bearer tokens for Hostinger API calls.
AI rationale
The flagged process execution is a build-time TypeScript compilation step, while the OAuth code uses Hostinger's auth service and stores credentials locally. The inspected entry points and request flow show no unrelated credential collection, transmission, or automatic account actions.
Evidence
~/.config/hostinger-mcp/credentials.json./dist
Network endpoints2
auth.hostinger.comdevelopers.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 manifest identifies this as a Hostinger API MCP server and points its main entry to the server implementation.
- OAuth uses Hostinger's auth service and a loopback callback for the sign-in flow.
- The OAuth flow exchanges the authorization code and PKCE verifier for tokens, then stores credentials under the user's configuration directory with restrictive Unix permissions.
- API bearer tokens are attached to requests sent to the Hostinger developer API.
- The flagged build script invokes the TypeScript compiler and copies project files into dist.
Evidence against
- No install lifecycle scripts are declared.
- The headless bootstrap's npx invocation occurs when that bootstrap is explicitly run and uses fixed package and command arguments.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsMinified
Source & flagged code
5 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 Critical5 High3 Medium4 Low
CriticalPrevious Version Dangerous Deltasrc/core/oauth.ts
HighChild Processbuild.js
HighShell
HighRuntime Package Installbuild.js
HighKnown Malware Source Similarityskills/headless/connect/bootstrap.mjs
HighKnown Malware Source Similaritybuild.js
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.20.3.
See all versions of @hostinger/mcp for other recorded verdicts.
- Review the evidence and your use of @hostinger/mcp@3.20.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.