Back to skill

Security audit

Notion Daily Journal

Security checks for vulnerabilities and agentic risk

Overview

This skill has a coherent daily-journal purpose, but it can automatically copy private Slack and DM content into Notion and send the page link to a fixed DM recipient without enough scoping or confirmation.

Review this skill before installing. It should only be used if the Notion destination, Slack and DM sources, timezone, and notification recipient are explicitly configured for the intended user. Prefer adding a confirmation step, private-source opt-in, redaction, and removal of the hard-coded DM identifier.

Vulnerability Patterns
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
  • 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
Findings (1)

T05 · Unauthorized Access and Privilege Escalation

Error
Location
SKILL.md:21
Finding

Private Workspace Data May Be Copied and Disclosed Through Unvalidated Fixed Destinations

Content
View full analysis

Vulnerability Details

File Location: SKILL.md, lines 21–26, 30–34, 62–67, and 73
Vulnerability Type: Excessive private-data access and insecure destination configuration
Risk Level: High

Vulnerable Code

markdown
**Slack** (`slack_search_public_and_private`):
- 今日自分が送ったメッセージ・参加したスレッド(`from:me after:today`)
- 今日決まったこと・アクションアイテム

**DM チャット** (`aachat_read_messages`):
- `dm:phase1demo.p-take55` の今日のやりとり(朝のブリーフィング内容・追加の依頼・完了報告)
markdown
環境変数 `NOTION_DAILY_JOURNAL_PAGE_ID` が設定されていればその親ページ(またはデータベース)を使う。未設定なら `notion-search` で "日報" や "Daily Log" を検索して特定する。

その日の日報ページが既にあれば `notion-update-page` で追記、なければ `notion-create-pages` で新規作成:
- タイトル: `{YYYY-MM-DD} 日報`
- 親: 上で特定したページまたはデータベース
markdown
`aachat_send_message` で `dm:phase1demo.p-take55` に投稿:

Notion 日報を更新しました: {YYYY-MM-DD} {Notion ページ URL}

text
markdown
- Slack・DM のプライベートな内容も個人ノート扱いで Notion に書いてよい

Technical Analysis

The skill explicitly searches public and private Slack content, reads a fixed direct-message conversation, and authorizes private Slack and DM information to be written into Notion. This collection scope is broader than the minimum access needed for a daily journal and lacks per-source consent, sensitivity filtering, or a preview-and-confirmation step.

The destination controls are also unsafe:

  1. If NOTION_DAILY_JOURNAL_PAGE_ID is unavailable, the skill selects a destination through a title search for generic names such as Daily Log. It does not require confirmation that the selected page belongs to the invoking user or has an appropriate sharing policy.
  2. The source DM and notification recipient are hard-coded as dm:phase1demo.p-take55, rather than being derived from the authenticated user or invocation context.
  3. The resulting Notion page URL is sent to that fixed recipient without validating that the recipient is authorized to receive it.

Consequently, installing o ...[truncated 1884 chars]

Remediation
View remediation

Remediation Suggestions

  1. Remove the hard-coded dm:phase1demo.p-take55 identifier. Derive both the source conversation and notification recipient from the authenticated invoking user and validated runtime context.
  2. Require explicit user approval before reading private channels or direct messages. Default collection to content authored by the user and to public sources.
  3. Allow the user to select individual sources and exclude channels, conversations, message types, or sensitivity classes.
  4. Require an explicitly configured and validated NOTION_DAILY_JOURNAL_PAGE_ID. Do not automatically write to a page selected only through a generic title search.
  5. If destination search remains supported, display all candidates and require user confirmation after showing page ownership, workspace, parent hierarchy, and sharing scope.
  6. Verify that the selected Notion destination is owned by or exclusively authorized for the invoking user before writing private information.
  7. Generate a preview of the proposed journal entry and require confirmation before transferring private Slack or DM content to Notion.
  8. Add redaction for credentials, personal data, confidential links, customer information, and other sensitive content.
  9. Validate the notification recipient immediately before sending the page URL, and avoid including the URL when recipient authorization cannot be established.
  10. Record auditable metadata identifying the approved sources, destination, invoking identity, and notification recipient without logging message contents or secrets.
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (5)

Missing User Warnings

High
Category
Not specified by scanner
Confidence
98% confidence
Finding

The skill instructs the agent to gather content from Slack and direct messages and place it into Notion, but it does not present a clear user-facing warning or consent mechanism for this transfer of potentially private information. This creates a significant privacy and data-handling risk because sensitive content may be copied into a different system with broader retention, searchability, or access controls.

Content

No source excerpt is available for this finding.

Ssd 3

High
Category
Not specified by scanner
Confidence
99% confidence
Finding

These instructions explicitly direct the agent to collect private Slack and DM content and copy it into Notion. Cross-system replication of private communications is dangerous because it can bypass the original audience boundaries, expand access to sensitive discussions, and create durable records in a platform with different permissions and retention settings.

Content

No source excerpt is available for this finding.

Ssd 3

High
Category
Not specified by scanner
Confidence
99% confidence
Finding

The note explicitly authorizes writing private Slack and DM contents into Notion on the assumption that it is a 'personal note,' but that assumption does not guarantee confidentiality or proper access control. This normalizes exfiltration of private communications into another datastore and increases the chance of privacy violations, unauthorized access, and retention of sensitive information beyond its original context.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
90% confidence
Finding

The skill schedules execution at 22:00 JST and later defines activity collection as "today (JST)" without offering any language or timezone choice. This is a natural-language locale policy issue because the file hard-codes a locale-specific behavior without opt-in or justification that the skill is intended only for a Japan-specific context.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

The manual trigger phrases are broad enough that ordinary conversation such as asking someone to 'write the daily report' could unintentionally invoke the skill. Because the skill reads from Slack, DM, and Linear and writes summaries into Notion, accidental activation can cause unintended collection and persistence of sensitive work communications.

Content

No source excerpt is available for this finding.