Back to skill

Security audit

Norwegian

Security checks for vulnerabilities and agentic risk

Overview

This is a simple Norwegian writing-style skill with no code execution, data access, persistence, or hidden behavior.

Install this if you want Norwegian text to sound casual and native-like. Be explicit when you need formal, conservative, Nynorsk, or dialect-specific writing, because the skill defaults toward informal Bokmal-style phrasing.

Vulnerability Patterns
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
Vulnerability Patterns
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (3)

Vague Triggers

Medium
Confidence
88% confidence
Finding
This is a markdown file, so vague-trigger review applies. The description only says "Write Norwegian that sounds human" without defining explicit trigger phrases, scope boundaries, or exclusion conditions, which makes invocation conditions ambiguous and could overlap with many ordinary Norwegian-writing requests.

Natural-Language Policy Violations

Medium
Confidence
94% confidence
Finding
The file directs the skill to default to an informal Norwegian register unless the user explicitly asks for formality. This imposes a specific locale/style behavior by default rather than offering a user choice or opt-in, which matches the policy's language/locale violation criterion.

Natural-Language Policy Violations

Medium
Confidence
91% confidence
Finding
These lines instruct the skill to always use "du" and never formal alternatives, regardless of user preference or context. Because the file does not offer opt-in or a choice of register, it enforces a specific language convention in a way the policy says to flag.

Static analysis

No suspicious patterns detected.