registry / @hostinger/mcp / 3.23.2
@hostinger/mcp@3.23.2
MCP server for Hostinger API
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe flagged process execution supports the build, and the headless bootstrap’s package installation and OAuth flow are only triggered by explicit invocation. The runtime’s default API endpoint belongs to Hostinger, and the inspected sources showed no automatic transmission of credentials or unrequested account actions.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
The server starts when launched as an MCP process; individual API operations require client tool calls. The separate headless bootstrap requires explicit invocation.
Impact
No automatic credential exfiltration, install-time contact, or unrequested account action was identified.
Mechanism
The runtime sends API requests to the configured Hostinger API base URL. The build script invokes the TypeScript compiler.
AI rationale
The flagged process execution supports the build, and the headless bootstrap’s package installation and OAuth flow are only triggered by explicit invocation. The runtime’s default API endpoint belongs to Hostinger, and the inspected sources showed no automatic transmission of credentials or unrequested account actions.
Network endpoints1
developers.hostinger.com
Decision evidence
public snapshotAI called this Clean at 95.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package is an MCP server for Hostinger’s API; its main entry starts the server with tools, instructions, and packaged skills.
- The build script runs `npx tsc` as part of compilation and writes build output; no install lifecycle scripts are declared.
- The runtime defaults API requests to `https://developers.hostinger.com`, with an optional user-configured API base URL.
- The headless bootstrap runs `npx` and may start OAuth login only when a user invokes that bootstrap script.
Evidence against
- The package exposes account-management tools that can make changes when called by an MCP client.
- The bootstrap reads cached Hostinger credentials to determine whether sign-in is needed.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsMinifiedUrlStrings
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 · L18skills/headless/connect/bootstrap.mjsView file
•matchType = normalized_sha256
matchedPackage = @hostinger/mcp@3.15.1
matchedPath = [redacted].mjs
matchedIdentity = npm:QGhvc3Rpbmdlci9tY3A:3.15.1
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
6 High3 Medium4 Low
HighChild Processbuild.js
HighShell
HighRuntime Package Installbuild.js
HighKnown Malware Source Similarityskills/headless/connect/bootstrap.mjs
HighKnown Malware Source Similarityskills/headless/steps/05-design/logo-kit.mjs
HighKnown Malware Source Similaritysrc/core/skills.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.23.2.
See all versions of @hostinger/mcp for other recorded verdicts.
- Review the evidence and your use of @hostinger/mcp@3.23.2 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.