hostinger-api-mcp@1.45.5
MCP server for Hostinger API
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe runtime can send a saved refresh token to an unrestricted issuer selected through OAUTH_ISSUER. Since the default issuer is Hostinger and the transfer depends on operator configuration, this warrants a warning for conditional credential exposure, not a publish block.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
An operator overrides OAUTH_ISSUER and an API tool call requires refreshing a saved token.
Impact
The configured recipient could receive a refresh token associated with the saved session.
Mechanism
The OAuth provider sends the saved refresh token to the configured issuer's token endpoint.
AI rationale
The runtime can send a saved refresh token to an unrestricted issuer selected through OAUTH_ISSUER. Since the default issuer is Hostinger and the transfer depends on operator configuration, this warrants a warning for conditional credential exposure, not a publish block.
Evidence
src/core/oauth.jssrc/core/runtime.js
Network endpoints2
auth.hostinger.comdevelopers.hostinger.com
Decision evidence
public snapshotAI called this Suspicious at 84.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The package entrypoint starts the runtime that handles API tool calls.
- The OAuth issuer can be overridden with OAUTH_ISSUER.
- When saved credentials have a refresh token, the OAuth flow uses it when refreshing access.
- The refresh request sends that token to the configured issuer's token endpoint.
- Runtime API calls obtain an OAuth token and place it in the Authorization header.
- The default OAuth and API endpoints are Hostinger services.
Evidence against
- Credential forwarding to another issuer requires an operator-configured issuer override and a refresh flow.
- The source defaults to Hostinger endpoints and does not establish a package-selected unrelated recipient.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
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.57.0
matchedIdentity = npm:aG9zdGluZ2VyLWFwaS1tY3A:1.57.0
similarity = 0.482
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
MediumAi Review Evidencepackage.json
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to hostinger-api-mcp@1.45.5.
See all versions of hostinger-api-mcp for other recorded verdicts.
- Review the evidence and your use of hostinger-api-mcp@1.45.5 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.