Natural-Language Policy Violations
- Category
- Not specified by scanner
- Confidence
- 87% confidence
- Finding
L003 的描述全文以中文定义技能用途,且文档中的回复模板、触发示例与交互方式均默认中文,没有说明是否支持其他语言或允许用户选择输出语言。根据规则,若技能对语言/locale 作出强制性默认而无用户选择或明确地域限定,属于自然语言策略问题。
- Content
Security audit
Security checks for vulnerabilities and agentic risk
This skill is a straightforward Chinese-language daily news helper that fetches news from a disclosed third-party API without hidden local access or persistence.
Install only if you are comfortable using a Chinese-language news tool that contacts api.cjiot.cc when invoked. Consider narrowing activation phrases or confirming before calls when a message only loosely mentions news.
L003 的描述全文以中文定义技能用途,且文档中的回复模板、触发示例与交互方式均默认中文,没有说明是否支持其他语言或允许用户选择输出语言。根据规则,若技能对语言/locale 作出强制性默认而无用户选择或明确地域限定,属于自然语言策略问题。
The trigger conditions include extremely broad keywords such as '新闻', '日报', and '头条', which can cause the skill to activate during ordinary conversation unrelated to the user's actual intent. Over-broad activation increases the chance of unintended external API calls and context capture, especially because the skill is designed to fetch remote content automatically.
This code includes natural-language documentation and console output in Chinese only, with no option for users to select another language or indication that the skill is intentionally limited to a Chinese-speaking audience. That creates a locale/language policy concern because the skill imposes a specific language without user opt-in.
The file’s natural-language interface is written entirely in Chinese, including the primary description and usage example, which effectively imposes a specific language on users. There is no indication that this skill is region-specific or that users can opt into another language, which matches the language/locale policy violation criteria.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
process.exit(1);
}
const url = `https://api.cjiot.cc/api/v1/daily?date=${date}`;
https.get(url, (res) => {
let data = '';
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
process.exit(1);
}
const url = `https://api.cjiot.cc/api/v1/daily?date=${date}`;
https.get(url, (res) => {
let data = '';
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
process.exit(1);
}
const url = `https://api.cjiot.cc/api/v1/daily?date=${date}`;
https.get(url, (res) => {
let data = '';
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
process.exit(1);
}
const url = `https://api.cjiot.cc/api/v1/daily?date=${date}`;
https.get(url, (res) => {
let data = '';
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
process.exit(1);
}
const url = `https://api.cjiot.cc/api/v1/daily?date=${date}`;
https.get(url, (res) => {
let data = '';
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
process.exit(1);
}
const url = `https://api.cjiot.cc/api/v1/daily?date=${date}`;
https.get(url, (res) => {
let data = '';
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
process.exit(1);
}
const url = `https://api.cjiot.cc/api/v1/daily?date=${date}`;
https.get(url, (res) => {
let data = '';