📦

Historial de auditorías

xhs-creator-collaboration-evaluation - 2 auditorías

Comparación de versiones

Cambios de capacidades y hallazgos entre versiones auditadas, primero las más recientes.

VersiónFechaResultadoElementos de revisiónCambio vs anterior
v2 Más reciente29 oct 2026, 04:56 Sin hallazgos confirmados2Sin cambios de capacidad
v1 21 oct 2026, 08:18 2 confirmado0Base

29 oct 2026, 04:56

Of 40 static findings, 38 are false positives involving Markdown, Chinese text, official links, credential configuration, or creator identifiers. Two command examples execute an unpinned npm package with automatic installation, creating dependency risk in an environment containing the API key. No evidence found of prompt injection, credential exfiltration, or concealed payloads in the two reviewed files; external package implementation was not reviewed.

2
Archivos escaneados
141
Líneas analizadas
5
Elementos de revisión
0
Falsos positivos ignorados
Elementos de revisión de capacidades (2)

Estas son capacidades locales reales que pueden esperarse para esta habilidad, por lo que requieren revisión, pero no se cuentan como comportamiento malicioso confirmado.

Medio
Ruby/shell backtick execution · 2 apariciones
```bash
The fence itself is Markdown, but its commands run npx -y socialdatax-skills@latest. This automatically executes mutable registry code with access to the configured API key.
Auditado por: codex

21 oct 2026, 08:18

All 39 static matches are false positives involving Markdown, legitimate authentication documentation, creator identifiers, and readable Chinese text. Separate semantic risks concern automatic execution of an unpinned npm package and forwarding payment links without destination validation. No evidence found of embedded malware, credential exfiltration, or prompt injection in the two supplied files; external package behavior was not reviewed.

2
Archivos escaneados
141
Líneas analizadas
5
Elementos de revisión
0
Falsos positivos ignorados

Preocupaciones de seguridad confirmadas (2)

Medio
Unpinned Third-Party Package Execution
CLI examples use 'npx -y socialdatax-skills@latest', automatically accepting a mutable npm release. A compromised release could execute locally with access to configured credentials.
The examples explicitly select latest and suppress the installation prompt with -y. This establishes a supply-chain exposure, not evidence that the package is malicious.
Medio
Unvalidated Payment Links From Error Responses
The instructions require displaying returned recharge links unchanged and encouraging payment. Without destination validation, a tampered response could redirect users to a phishing site.
The payment workflow explicitly trusts error-supplied URLs without a hostname check. The provider-domain restriction addresses API key management, not these returned billing links.
Auditado por: codex