Versioned security assessment

Report ID: SA-64CA8AF0

7/8/2026, 12:47:04 PM

maxhub-tiktok security assessment v3

Skill Security Certification Report

Audit History
Audit model: codex Historical report
Skill name
maxhub-tiktok
Version
v3
Maintainer
XieWxx
Coverage
9 Files scanned · 9,970 Lines analyzed
Policy version
Unavailable

Highest confirmed finding severity

High

3 confirmed security findings require attention.

Installation context

Historical evidence

This report may not describe the currently installable artifact. Open the current Skill page for install guidance.

Open current Skill page

This report does not block or authorize the manifest or ZIP.

Most static hits are Markdown documentation false positives, including backticks, endpoint IDs, sample URLs, and bilingual text. Confirmed risk remains because the skill handles a MaxHub API key, may transmit TikTok cookies, and documents anti-abuse and interaction capabilities.

Report position

Historical report

Open audit history before using this report to install.

Audit attestation

Not attestable

The required immutable binding is incomplete.

Human verification

Not verified

No human verification is recorded for this report.

Coverage

9 Files scanned · 9,970 Lines analyzed

12 items shown for review

Limitations

This report does not claim runtime or sandbox execution and does not prove the absence of side effects.

Evidence chain

Follow the evidence from source binding to the install contract. Available evidence supports verification; it is not a safety guarantee.

  1. Source

    Binding unavailable

  2. Artifact

    Identity incomplete

  3. Audit

    Complete

  4. Install contract

    Open manifest to verify

    Open manifest

Capabilities observed

Observed means this report recorded supporting evidence. Not recorded does not prove that a capability is absent.

Contains scripts

May execute code included with the Skill.

Not recorded by this audit

Network access

May connect to external services.

Observed in 64 evidence locations

Filesystem access

May read or write local files.

Not recorded by this audit

Env variables

May read values from the process environment.

Observed in 16 evidence locations

External commands

May invoke commands or programs outside the Skill.

Observed in 19 evidence locations

Capability review items (9)
High
Generic API/secret keys
Auth: `Authorization: Bearer $MAXHUB_API_KEY`
This instructs use of MAXHUB_API_KEY as a Bearer token for MaxHub API calls. The token is intentionally sent to a third-party service.
High
Generic API/secret keys
Auth: `Authorization: Bearer $MAXHUB_API_KEY`
This instructs use of MAXHUB_API_KEY as a Bearer token for MaxHub API calls. The token is intentionally sent to a third-party service.
High
Generic API/secret keys
Auth: `Authorization: Bearer $MAXHUB_API_KEY`
This instructs use of MAXHUB_API_KEY as a Bearer token for MaxHub API calls. The token is intentionally sent to a third-party service.
High
Generic API/secret keys
Auth: `Authorization: Bearer $MAXHUB_API_KEY`
This instructs use of MAXHUB_API_KEY as a Bearer token for MaxHub API calls. The token is intentionally sent to a third-party service.
High
Generic API/secret keys
primaryEnv: MAXHUB_API_KEY
The skill declares MAXHUB_API_KEY as a required sensitive environment value. This is expected for the API integration but grants the skill access to a secret.
High
Generic API/secret keys
- MAXHUB_API_KEY
The skill declares MAXHUB_API_KEY as a required sensitive environment value. This is expected for the API integration but grants the skill access to a secret.
High
Generic API/secret keys
- name: MAXHUB_API_KEY
The skill declares MAXHUB_API_KEY as a required sensitive environment value. This is expected for the API integration but grants the skill access to a secret.
High
Generic API/secret keys
Use the configured `MAXHUB_API_KEY` value as the `Authorization: Bearer` request header.
This instructs use of MAXHUB_API_KEY as a Bearer token for MaxHub API calls. The token is intentionally sent to a third-party service.
High
Generic API/secret keys
maxhub_auth_header="Authorization: Bearer ${MAXHUB_API_KEY}"
This instructs use of MAXHUB_API_KEY as a Bearer token for MaxHub API calls. The token is intentionally sent to a third-party service.

Risk findings

Confirmed security concerns are separated from items that still need review.

Confirmed security concerns (3)

RISK-001 High
Credential and Session Cookie Transmission to Third Party
The skill sends MAXHUB_API_KEY as a Bearer token to MaxHub and warns that some endpoints may require platform session cookies.
The credential header and cookie requirements are explicit in the skill and reference files. This is intentional third-party credential handling, not scanner noise.
RISK-002 High
Anti-Abuse Token and Guest Cookie Generation
The references include endpoints for TikTok encryption headers, guest cookies, real msToken generation, and randomized browser fingerprint data.
The documentation directly describes generating TikTok request headers, guest cookies, and randomized browser fingerprint data for crawler resistance.
RISK-003 High
Read-Only Claim Conflicts With Interaction Actions
The skill claims read-only operation, but README content lists like, follow, comment, collect, and forward actions, and references include private-message deep links.
The read-only statement is explicit, while separate files advertise interaction actions and a private-message deep link. Some actions may only generate links, but the scope mismatch is real.

Remediation

Suggested fixes recorded by this audit. Applying them is the maintainer’s responsibility.

  1. FIX-001
    High
    Third-party credential and cookie transmission
    Require explicit user consent before sending API keys or TikTok cookies. Recommend scoped or test credentials and document provider retention behavior.
  2. FIX-002
    High
    Anti-abuse token, fingerprint, and guest-cookie tooling
    Remove or gate endpoints for signatures, device identifiers, msToken, web_id, and guest cookies unless policy approval is documented.
  3. FIX-003
    High
    Read-only claim conflicts with interaction capabilities
    Remove like, follow, comment, forward, and private-message capabilities, or separate them with explicit warnings and confirmation requirements.
  4. FIX-004
    Low
    Static scanner noise from Markdown formatting
    Break very long endpoint tables into shorter sections and avoid ambiguous shell-style backticks where plain text works.

Expert evidence

Immutable subject identity, scanner metadata, dismissed matches, and source-level evidence.

Artifact subject

Marketplace commit
Unavailable
Content hash
Unavailable
Tree hash
Unavailable
Skill path
Unavailable
Audit payload hash
Unavailable

Analysis metadata

Audit model: codex

Analysis state: Complete

Scope is limited to the recorded files, lines, methods, and evidence. No runtime or sandbox execution is claimed.

Verify and export

The manifest and lockfile bind install artifacts to cryptographic hashes. This integrity claim is separate from the security assessment.

Audit attestation: not_attestable