Back to skill

Security audit

DDD领域驱动设计技能

Security checks for vulnerabilities and agentic risk

Overview

This is a DDD guidance skill made of Markdown reference material, with no hidden execution, persistence, credential use, or exfiltration behavior found.

Install only if you want Chinese-language DDD guidance. Before copying generated Gradle examples into a real project, pin exact dependency versions and review the event-publishing examples for correct transaction semantics.

Vulnerability Patterns
  • Insecure DependenciesIntroduces malicious components through unsafe dependency sources
  • 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)

T08 · Insecure Dependencies

Warning
Location
ddd-architecture/references/gradle-dependencies.md:15
Finding

Mutable Gradle Plugin Versions Undermine Build Reproducibility and Supply-Chain Integrity

Content
View full analysis

Vulnerability Details

File Location: ddd-architecture/references/gradle-dependencies.md, lines 15–22
Vulnerability Type: Mutable third-party dependency versions
Risk Level: Medium

Vulnerable Code

groovy
plugins {
    id 'java'
    id 'org.springframework.boot' version '3.2.x' apply false
    id 'io.spring.dependency-management' version '1.1.x' apply false
}

ext {
    set('springBootVersion', '3.2.x')
}

Technical Analysis

The Gradle template uses the wildcard version 3.2.x for Spring Boot and 1.1.x for the Spring dependency-management plugin. These mutable selectors can resolve to different releases over time without any corresponding source-code change.

Because Gradle plugins execute code during build configuration and execution, resolving an unreviewed matching release expands the build's supply-chain trust boundary. The use of recognized plugin identifiers and standard repositories reduces the likelihood of dependency confusion or typosquatting, but wildcard versions still prevent deterministic review and make it possible for future releases, compromised artifacts, or vulnerable transitive dependencies to enter generated projects automatically.

Attack Path

  1. A user follows the Skill guidance and copies the provided Gradle configuration into a project.
  2. Gradle queries the configured plugin and artifact repositories for versions matching 3.2.x and 1.1.x.
  3. A later matching release is published after the original configuration was reviewed.
  4. A subsequent build resolves that new release instead of a previously reviewed artifact.
  5. Gradle loads and executes the plugin under the privileges of the build process.
  6. If the newly resolved artifact is compromised or contains a security regression, it can affect the build environment and generated application without a source-code change alerting reviewers.

Impact Assessment

A malicious Gradle plugin could ...[truncated 566 chars]

Remediation
View remediation

Remediation Suggestions

  • Replace every wildcard selector with an exact, reviewed version, for example:

    groovy
    plugins {
        id 'java'
        id 'org.springframework.boot' version '3.2.12' apply false
        id 'io.spring.dependency-management' version '1.1.7' apply false
    }
    
    ext {
        set('springBootVersion', '3.2.12')
    }
    
  • Verify that the selected versions are supported and free of known vulnerabilities before documenting them.

  • Enable Gradle dependency locking and commit the generated lock files.

  • Enable Gradle dependency verification using trusted checksums or signatures and commit gradle/verification-metadata.xml.

  • Restrict plugin and dependency resolution to an explicit allowlist of trusted repositories.

  • Configure CI to reject dynamic versions such as +, latest.release, and version wildcards.

  • Use automated dependency-update tooling to propose explicit, reviewable version changes rather than silently accepting future releases.

  • Review transitive dependency changes and run security scanning whenever pinned versions are upgraded.

Vulnerability Patterns
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (23)

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
93% confidence
Finding

L03 将适用场景描述为“当用户提到 DDD 领域驱动设计、或需要全面覆盖新项目开发、老项目重构、架构规范、战术设计、代码审查等多个维度时使用”。前半句较明确,但后半句覆盖了大量常见开发活动,未限定必须与 DDD 明确相关,也没有给出不应触发的反例,容易与日常项目、重构或审查请求重叠。

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The manifest description is written entirely in Chinese and describes the skill’s use conditions in that language, which can impose a language/locale requirement on users without offering a choice or documenting that the skill is region-specific. This matches the policy category for language or locale constraints lacking user opt-in.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
92% confidence
Finding

The manifest description is entirely in Chinese and presents the skill as a Chinese-language code review checklist without indicating that users may choose another language. Under the policy, forcing a specific language without opt-in is a natural-language policy violation unless the locale restriction is explicitly justified.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
93% confidence
Finding

The skill metadata and content are presented in Chinese, but there is no indication that the user can choose the language or that the skill is intentionally limited to Chinese-speaking contexts. This can violate language or locale policy when users have not opted into that language.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
93% confidence
Finding

The skill declares broad activation triggers such as '当用户提到新建 DDD 项目、从零搭建 DDD、从事件风暴开始项目设计时使用', which can cause the agent to invoke this skill in loosely related conversations without strong scoping. While the content itself is non-malicious and procedural, over-broad routing can misapply the skill, leading to irrelevant guidance, reduced user control, or accidental chaining into additional project-generation actions.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The entire document is written as Chinese-only instructional content, and it does not offer an alternative language, opt-in, or explain that the skill is intended only for a Chinese-speaking or region-specific audience. Under the stated policy, forcing a specific language without user choice is a natural-language policy violation.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
93% confidence
Finding

The skill content is entirely in Chinese and its metadata/usage guidance implicitly constrains interaction language without any user opt-in or fallback. This can reduce transparency and cause the agent to ignore the user's preferred language, which is a prompt-quality and instruction-compliance issue rather than a direct code-execution risk.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
93% confidence
Finding

This markdown file presents all instructional content in a single language and does not indicate that Chinese is an optional or region-specific presentation. Under the policy rule for natural-language violations, forcing a specific language without user opt-in is in scope.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

The description says to use the skill when the user mentions topics like DDD coding, entity design, value objects, aggregates, repository patterns, or domain events. These are broad conceptual mentions rather than narrowly defined invocation triggers, and the file provides no exclusion conditions or negative examples to distinguish casual discussion from intentional skill use.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
90% confidence
Finding

The description is written as a Chinese-language skill specification and presents the skill purpose in Chinese without indicating that language selection is optional or user-driven. Under the language/locale policy, forcing a specific language without user opt-in can be a natural-language policy violation unless the locale restriction is clearly justified.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

This markdown file is entirely written in Chinese and does not indicate that the language choice is optional, configurable, or limited to a justified region-specific context. Under the policy, forcing a specific language without user opt-in is a natural-language policy violation.

Content

No source excerpt is available for this finding.

Intent-Code Divergence

Medium
Category
Not specified by scanner
Confidence
96% confidence
Finding

The documentation states that events are published after transaction commit, but the example uses a TransactionTemplate call inside a @Transactional method rather than a real after-commit callback. This can mislead implementers into publishing events before the surrounding transaction is durably committed, causing consumers to observe state that later rolls back or does not yet exist consistently.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
90% confidence
Finding

The file title and all instructional content are written exclusively in Chinese, which effectively imposes a specific language on users. The document does not offer an alternative language, opt-in, or a stated region-specific justification, matching the language/locale policy violation criteria.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The entire skill reference is written only in Chinese and does not indicate that language selection is optional or limited to a justified region-specific context. Under the policy, forcing a specific language without user opt-in is a natural-language locale violation.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
85% confidence
Finding

L72 说明“本套件所有代码示例以 Java/Kotlin + Spring/JPA 生态为主”,这属于对输出语言/技术栈的固定约束,但未说明可根据用户偏好切换。按规则,强制特定语言或 locale 且无用户 opt-in 属于自然语言策略问题。

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
91% confidence
Finding

This markdown file uses a single fixed language throughout and does not mention that the content is intended for a Chinese-speaking audience or offer an alternative language. Under the policy criteria, forcing a specific language without user opt-in can be a natural-language policy violation.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
92% confidence
Finding

该文件从标题开始整体以中文呈现,未见任何关于语言可选、用户可切换语言,或该技能仅适用于特定语言/地区场景的说明。按规则,若技能内容强制特定语言且没有用户选择或明确正当理由,可构成自然语言层面的语言/locale 策略问题。

Content

No source excerpt is available for this finding.

Vague Triggers

Low
Category
Not specified by scanner
Confidence
88% confidence
Finding

The manifest description says to use the skill when the user mentions broad topics such as DDD design, domain modeling, bounded contexts, ubiquitous language, or strategic design. While domain-related, it does not define boundaries, explicit trigger phrases, or negative examples, which could cause the skill to activate in loosely related architecture discussions.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
90% confidence
Finding

This markdown file is entirely Chinese-language instructional content, and there is no indication that the skill offers users a language/locale choice or that the Chinese-only constraint is justified by a region-specific purpose. Under the policy, forcing a specific language without user opt-in is a natural-language policy violation.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
86% confidence
Finding

This markdown file presents the glossary template, instructions, and examples entirely in Chinese, while only partially translating the title with an English parenthetical. Under the policy rule for natural-language violations, this can be considered a language constraint because the skill does not offer the user a language choice or state that the content is intentionally limited to a Chinese-speaking context.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
95% confidence
Finding

This markdown file contains all user-facing guidance in Chinese, and nowhere indicates that the user may choose another language or that the skill is intentionally restricted to a Chinese-speaking audience. The policy specifically calls for flagging language/locale constraints when they are imposed without opt-in or justification.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
91% confidence
Finding

This markdown file contains user-facing instructional content solely in Chinese, and there is no indication that the skill is region-specific or that users can opt into another language. Under the policy, forcing a specific language without user choice or justification is a natural-language policy concern.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
94% confidence
Finding

The entire skill document is written in Chinese and does not offer any language or locale choice, nor does it explain that the content is intended only for a Chinese-speaking or region-specific audience. Under the stated policy, forcing a specific language without opt-in is a natural-language policy violation.

Content

No source excerpt is available for this finding.