hostinger-api-mcp@1.60.0
MCP server for Hostinger API
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe source does not establish malicious intent or install-time execution; the flagged build command compiles TypeScript, and the default OAuth issuer is Hostinger. A crafted operator-supplied OAUTH_ISSUER can nevertheless reach a shell command during login, so this warrants a warning for conditional local command execution.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
OAuth login runs explicitly or during authentication when no environment token or usable saved credentials are available, and OAUTH_ISSUER contains shell syntax.
Impact
If an attacker can control OAUTH_ISSUER, they can run commands with the package user's privileges.
Mechanism
The issuer contributes to the authorization URL, which is interpolated into a platform shell command and executed.
AI rationale
The source does not establish malicious intent or install-time execution; the flagged build command compiles TypeScript, and the default OAuth issuer is Hostinger. A crafted operator-supplied OAUTH_ISSUER can nevertheless reach a shell command during login, so this warrants a warning for conditional local command execution.
Evidence
src/core/oauth.jssrc/core/runtime.js
Network endpoints1
auth.hostinger.com
Decision evidence
public snapshotAI called this Suspicious at 88.0% confidence as Critical Vulnerability with medium false-positive risk.
Evidence for warning
- The build script is a TypeScript compilation command, not an install hook.
- OAuth takes its issuer from the OAUTH_ISSUER environment variable when set.
- Without an environment token or usable saved credentials, runtime authentication can start the OAuth login flow; login can also be requested explicitly.
- The issuer is used to construct the authorization URL, which is passed to the browser launcher.
- The launcher inserts that URL into a shell command and runs it with exec, creating conditional command injection if the issuer value is attacker-controlled.
- The default OAuth issuer is Hostinger; API requests send a bearer token to the URL built from the configured API base and tool path.
Evidence against
- The manifest lists start, build, and start:ts scripts; build.js runs the TypeScript compiler.
- The default OAuth issuer is Hostinger, and API requests are made through the configured API endpoint.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystem
Source & flagged code
4 flagged · loading sourcebuild.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 · L18src/core/oauth.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = hostinger-api-mcp@1.59.0
matchedIdentity = npm:aG9zdGluZ2VyLWFwaS1tY3A:1.59.0
similarity = 0.946
summary = stored previous version shares package body but lacks this dangerous source file
Critical
Previous Version Dangerous Delta
This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
src/core/oauth.jsFindings
1 Critical3 High4 Medium4 Low
CriticalPrevious Version Dangerous Deltasrc/core/oauth.js
HighChild Processbuild.js
HighShell
HighRuntime Package Installbuild.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
MediumSuspicious Lifecycle Evidencepackage.json
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to hostinger-api-mcp@1.60.0.
See all versions of hostinger-api-mcp for other recorded verdicts.
- Review the evidence and your use of hostinger-api-mcp@1.60.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.