registry / @hostinger/mcp / 3.16.0
@hostinger/mcp@3.16.0
MCP server for Hostinger API
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe package is a Hostinger API MCP server. Its flagged shell execution is confined to an explicitly invoked build script, and OAuth credentials are sent to the Hostinger auth service for the expected sign-in and refresh flows.
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 an entry point is invoked; OAuth sign-in or token refresh occurs when requested by the user or when an API call needs authentication.
Impact
Expected Hostinger API access and local OAuth credential storage; no unrelated collection or execution behavior was identified.
Mechanism
The server exposes Hostinger API tools. OAuth tokens are exchanged with the configured issuer, which defaults to Hostinger’s auth service. The build script invokes the TypeScript compiler when explicitly run.
AI rationale
The package is a Hostinger API MCP server. Its flagged shell execution is confined to an explicitly invoked build script, and OAuth credentials are sent to the Hostinger auth service for the expected sign-in and refresh flows.
Evidence
~/.config/hostinger-mcp/credentials.json
Network endpoints1
auth.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 package exposes Hostinger MCP server entry points and has no install lifecycle scripts.
- The flagged build script runs `npx tsc` only when the build script is explicitly invoked.
- OAuth uses Hostinger’s auth service by default, and refresh tokens are sent there as part of the refresh-token flow.
- The main entry imports the server runtime, tools, instructions, and skills, then starts the MCP server.
Evidence against
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.16.0.
See all versions of @hostinger/mcp for other recorded verdicts.
- Review the evidence and your use of @hostinger/mcp@3.16.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.