Security audit
Security checks for vulnerabilities and agentic risk
The skill is read-only and purpose-aligned, but it asks agents to run an unpinned npm package at runtime while using an API key.
Install only if you are comfortable running the SocialDataX npm CLI from the public registry and exposing `SOCIALDATAX_API_KEY` to that process. Prefer a pinned, reviewed package version or a controlled MCP/tool installation before using it in a sensitive environment.
The skill invokes npx -y socialdatax-skills@latest, which fetches and executes the latest package version at runtime rather than a pinned, reviewed release. If the upstream package is compromised, typo-squatted, or a malicious update is published, an agent running this skill could execute attacker-controlled code immediately in the local environment.
Using npx -y socialdatax-skills@latest causes runtime installation and execution of whatever code is currently published as the latest version. This creates a supply-chain execution path where a compromised maintainer account or malicious release can lead to arbitrary code execution on the host running the skill.
The command references an unpinned package version, so the behavior and code executed can change without notice between runs. In agent environments, this is especially risky because package install hooks or the CLI itself may access local files, network resources, or environment variables such as SOCIALDATAX_API_KEY.
By instructing agents to run npx -y ...@latest, the skill delegates trust to the current npm registry state at execution time. An attacker who gains control of the package or its dependency chain could deliver malicious code that runs under the agent's privileges.
This line repeats the same unpinned runtime package execution pattern, exposing the environment to supply-chain compromise. Because the skill is designed for agent use and may run with network access and secrets configured, successful exploitation could go beyond incorrect output and result in host compromise or secret exfiltration.
The unpinned @latest reference is a real supply-chain risk because it allows silent code changes without modification to the skill file itself. In this skill's context, the danger is somewhat elevated because the documented workflow expects an API key in the environment, which malicious package code could read or exfiltrate.
No suspicious patterns detected.
