registry / @hostinger/mcp / 3.28.0
@hostinger/mcp@3.28.0
MCP server for Hostinger API
AI Security Review
scanned 16h ago · by lpm-firewall-aiThe manifest declares no install hooks, and the credential flow inspected sends Hostinger credentials to Hostinger services. The new polling helper is explicitly invoked and serves the package’s Hostinger workflow; the scanner’s credential-redirection and runtime-install leads were not substantiated in the inspected source.
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 as a command or MCP entry point; the added wait helper runs when explicitly called.
Impact
Expected Hostinger API operations using the user's configured token or sign-in; no unrelated credential transfer or automatic harmful action was found.
Mechanism
OAuth and API requests use Hostinger endpoints. The helper polls the local MCP server for Hostinger job status.
AI rationale
The manifest declares no install hooks, and the credential flow inspected sends Hostinger credentials to Hostinger services. The new polling helper is explicitly invoked and serves the package’s Hostinger workflow; the scanner’s credential-redirection and runtime-install leads were not substantiated in the inspected source.
Evidence
src/core/oauth.jssrc/core/runtime.jsskills/headless/wait.mjs
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 has no lifecycle hooks; its entry points are Hostinger MCP server commands.
- OAuth defaults to Hostinger’s auth service, and API requests send the bearer token to the configured Hostinger API base URL.
- The added wait script is described as a polling helper and is invoked by explicit skill steps; it does not run automatically on import or install.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsMinifiedUrlStrings
Source & flagged code
8 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/mcp@3.27.1
matchedPath = build.js
matchedIdentity = npm:QGhvc3Rpbmdlci9tY3A:3.27.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.
build.jsView on unpkgsrc/core/skills.jsView file
Findings
1 Critical8 High3 Medium4 Low
CriticalPrevious Version Dangerous Deltaskills/headless/wait.mjs
HighChild Processbuild.js
HighShell
HighCredential Redirect Persistencesrc/core/skills.js
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
Affected versions and remediation
This report applies to @hostinger/mcp@3.28.0.
See all versions of @hostinger/mcp for other recorded verdicts.
- Review the evidence and your use of @hostinger/mcp@3.28.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.