Security audit
Security checks for vulnerabilities and agentic risk
The skill appears to provide Naver/Korean search as advertised, but it runs an unpinned third-party npm MCP server with Naver API credentials.
Review this skill before installing. Prefer a pinned, vetted version of the npm MCP server, store the Naver API keys only in the skill's intended secret configuration, do not commit or paste them into chats or logs, and rotate them if exposed.
The description says the skill is for 'Korean web search' and the guidance repeatedly directs use for Korean-source results. That creates a locale-specific constraint, but the file does not explicitly present it as a user opt-in choice or justify the restriction as a region-specific tool in policy terms.
The skill metadata installs and runs an npm-published MCP server without pinning an exact version, which creates a supply-chain risk. A future compromised or malicious package release could be pulled automatically during install or execution and would run with access to configured API credentials and the local environment.
The documented command npx -y @isnow890/naver-search-mcp fetches and executes the latest package version at runtime, which is a classic unpinned remote-code execution path. If the npm account or package is hijacked, users may execute attacker-controlled code that can access Naver API secrets exposed through environment variables.
This markdown file instructs users to supply NCP_APIGW_API_KEY, NCP_APIGW_API_KEY_ID, NAVER_CLIENT_ID, and NAVER_CLIENT_SECRET, which are sensitive secrets. While it explains how to configure them, it does not include a user-facing warning not to expose, commit, or share these credentials, which is a privacy and account-safety relevant omission under the markdown warning criterion.
