Property Shared— mcp server

Property Shared — independently scanned and version-tracked by SaferSkills.

by paulieb89·MCP Server·github.com/paulieb89/property-shared

Is Property Shared safe to install?

SaferSkills independently audited Property Shared (MCP Server) and scored it 45/100 (orange). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 126 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

Score
45/100
●●●●●○○○○○
↑ +0 since first scan (45 → 45)Re-scan~30s
Latest scan
ScannedJun 24, 2026 · 29d ago
Scans run1 over 90 days
Detectors55 checks · 5 categories
Findings0 warnings · 126 high
EngineSaferSkills 2b638c6
View methodology →
SaferSkills installs
This week0
This month0
All time0
CategoryWeightCategory scoreContribution
Securityprompt, exec, net, exfil, eval
35%
0
0.0 pts
Supply chainhash, typosquat, maintainer, lockfile
20%
100
20.0 pts
Maintenancestaleness, pinning, CI
15%
100
15.0 pts
TransparencySKILL.md, perms, README
15%
100
15.0 pts
Communityinstalls, verify, response
15%
100
15.0 pts

Findings & checks · 126 flagged

Securityscore 0 · 126 findings
HIGHLong base64-encoded blob hidden in the skill documentationSS-SKILL-INJECT-B64-PAYLOAD-01 · Prompt injection · docs/prefab/actions/open-file-picker.md
HIGHonce decoded by the agent, an encoded payload has the same impact class as plain-text injection.
Why it matters

A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.

The exact value spotted
excerptdocs/prefab/actions/open-file-picker.md· markdown
244</Info>
245 
246<ComponentPreview json={{"view":{"type":"Button","label":"Upload File","variant":"default","
… (108 chars elided on L246)
247<CodeGroup>
248```python Python icon="python" theme={"theme":{"light":"snazzy-light","dark":"dark-plus"}}
Occurrences
1 occurrence · at L246
How to fix
Remove the encoded blob, or decode it and review what it actually contains.
  1. Decode the base64 string and confirm it is not an instruction directed at the agent.
  2. Move any legitimate binary or signature data into a dedicated file (*.sig, SIGNATURES) outside the documentation.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-B64-PAYLOAD-01sha2569f6c233d05fbbc21rubric 365aacaView on GitHub
HIGHLong base64-encoded blob hidden in the skill documentationSS-SKILL-INJECT-B64-PAYLOAD-01 · Prompt injection · docs/prefab/actions/request-display-mode.md
HIGHonce decoded by the agent, an encoded payload has the same impact class as plain-text injection.
Why it matters

A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.

The exact value spotted
excerptdocs/prefab/actions/request-display-mode.md· markdown
266Use the `HOST` reactive variable to show the right button based on the current display mode.
… (80 chars elided on L266)
267 
268<ComponentPreview json={{"view":{"type":"Column","children":[{"type":"Condition","cases":[{"
… (108 chars elided on L268)
269<CodeGroup>
270```python Python icon="python" theme={"theme":{"light":"snazzy-light","dark":"dark-plus"}}
Occurrences
1 occurrence · at L268
How to fix
Remove the encoded blob, or decode it and review what it actually contains.
  1. Decode the base64 string and confirm it is not an instruction directed at the agent.
  2. Move any legitimate binary or signature data into a dedicated file (*.sig, SIGNATURES) outside the documentation.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-B64-PAYLOAD-01sha256d54dfe54a025cd41rubric 365aacaView on GitHub
HIGHLong base64-encoded blob hidden in the skill documentationSS-SKILL-INJECT-B64-PAYLOAD-01 · Prompt injection · docs/prefab/actions/send-message.md
HIGHonce decoded by the agent, an encoded payload has the same impact class as plain-text injection.
Why it matters

A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.

The exact value spotted
excerptdocs/prefab/actions/send-message.md· markdown
238`SendMessage` puts words in the user's mouth — when triggered, it sends a message to the con
… (108 chars elided on L238)
239 
240<ComponentPreview json={{"view":{"type":"Button","label":"Summarize","variant":"default","si
… (108 chars elided on L240)
241<CodeGroup>
242```python Python icon="python" theme={"theme":{"light":"snazzy-light","dark":"dark-plus"}}
Occurrences
1 occurrence · at L240
How to fix
Remove the encoded blob, or decode it and review what it actually contains.
  1. Decode the base64 string and confirm it is not an instruction directed at the agent.
  2. Move any legitimate binary or signature data into a dedicated file (*.sig, SIGNATURES) outside the documentation.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-B64-PAYLOAD-01sha25687613ac3d7a8c3b9rubric 365aacaView on GitHub
HIGHLong base64-encoded blob hidden in the skill documentationSS-SKILL-INJECT-B64-PAYLOAD-01 · Prompt injection · docs/prefab/actions/set-interval.md
HIGHonce decoded by the agent, an encoded payload has the same impact class as plain-text injection.
Why it matters

A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.

The exact value spotted
excerptdocs/prefab/actions/set-interval.md· markdown
242Set `count=1` to fire once after a pause — no separate "delay" action needed. Put your logic
… (108 chars elided on L242)
243 
244<ComponentPreview json={{"view":{"type":"Button","label":"{{ waiting ? 'Waiting\u2026' : 'St
… (108 chars elided on L244)
245<CodeGroup>
246```python Python icon="python" theme={"theme":{"light":"snazzy-light","dark":"dark-plus"}}
Occurrences
1 occurrence · at L244
How to fix
Remove the encoded blob, or decode it and review what it actually contains.
  1. Decode the base64 string and confirm it is not an instruction directed at the agent.
  2. Move any legitimate binary or signature data into a dedicated file (*.sig, SIGNATURES) outside the documentation.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-B64-PAYLOAD-01sha2564e81d69e4aba4015rubric 365aacaView on GitHub
HIGHLong base64-encoded blob hidden in the skill documentationSS-SKILL-INJECT-B64-PAYLOAD-01 · Prompt injection · docs/prefab/actions/show-toast.md×3
HIGHonce decoded by the agent, an encoded payload has the same impact class as plain-text injection.
Why it matters

A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.

The exact value spotted
excerptdocs/prefab/actions/show-toast.md· markdown
238`ShowToast` displays a brief notification. It's a client-side action — no server round-trip
… (108 chars elided on L238)
239 
240<ComponentPreview json={{"view":{"cssClass":"gap-2","type":"Row","children":[{"type":"Button
… (108 chars elided on L240)
241<CodeGroup>
242```python Python icon="python" theme={"theme":{"light":"snazzy-light","dark":"dark-plus"}}
Occurrences
3 occurrences · first at L240, also L289, L418
Show all 3 locations
Line
File
L240
docs/prefab/actions/show-toast.md
L289
docs/prefab/actions/show-toast.md
L418
docs/prefab/actions/show-toast.md
How to fix
Remove the encoded blob, or decode it and review what it actually contains.
  1. Decode the base64 string and confirm it is not an instruction directed at the agent.
  2. Move any legitimate binary or signature data into a dedicated file (*.sig, SIGNATURES) outside the documentation.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-B64-PAYLOAD-01sha2563cd4b525605fd57arubric 365aacaView on GitHub
HIGHLong base64-encoded blob hidden in the skill documentationSS-SKILL-INJECT-B64-PAYLOAD-01 · Prompt injection · docs/prefab/actions/update-context.md
HIGHonce decoded by the agent, an encoded payload has the same impact class as plain-text injection.
Why it matters

A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.

The exact value spotted
excerptdocs/prefab/actions/update-context.md· markdown
282For richer data, pass a dict instead of plain text:
283 
284<ComponentPreview json={{"view":{"cssClass":"gap-3","type":"Column","children":[{"name":"thi
… (108 chars elided on L284)
285<CodeGroup>
286```python Python icon="python" theme={"theme":{"light":"snazzy-light","dark":"dark-plus"}}
Occurrences
1 occurrence · at L284
How to fix
Remove the encoded blob, or decode it and review what it actually contains.
  1. Decode the base64 string and confirm it is not an instruction directed at the agent.
  2. Move any legitimate binary or signature data into a dedicated file (*.sig, SIGNATURES) outside the documentation.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-B64-PAYLOAD-01sha25669435efcd838ed38rubric 365aacaView on GitHub
HIGHLong base64-encoded blob hidden in the skill documentationSS-SKILL-INJECT-B64-PAYLOAD-01 · Prompt injection · docs/prefab/actions/update-state.md
HIGHonce decoded by the agent, an encoded payload has the same impact class as plain-text injection.
Why it matters

A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.

The exact value spotted
excerptdocs/prefab/actions/update-state.md· markdown
450`ToggleState` flips a boolean — `True` becomes `False`, `False` becomes `True`. Pair it with
… (54 chars elided on L450)
451 
452<ComponentPreview json={{"view":{"cssClass":"gap-2","type":"Column","children":[{"type":"But
… (108 chars elided on L452)
453<CodeGroup>
454```python Python icon="python" theme={"theme":{"light":"snazzy-light","dark":"dark-plus"}}
Occurrences
1 occurrence · at L452
How to fix
Remove the encoded blob, or decode it and review what it actually contains.
  1. Decode the base64 string and confirm it is not an instruction directed at the agent.
  2. Move any legitimate binary or signature data into a dedicated file (*.sig, SIGNATURES) outside the documentation.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-B64-PAYLOAD-01sha25645ce9c7734dd8ed2rubric 365aacaView on GitHub
HIGHLong base64-encoded blob hidden in the skill documentationSS-SKILL-INJECT-B64-PAYLOAD-01 · Prompt injection · docs/prefab/components/accordion.md
HIGHonce decoded by the agent, an encoded payload has the same impact class as plain-text injection.
Why it matters

A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.

The exact value spotted
excerptdocs/prefab/components/accordion.md· markdown
401Set `multiple=True` to allow more than one section open at a time.
402 
403<ComponentPreview json={{"view":{"type":"Accordion","multiple":true,"collapsible":true,"defa
… (108 chars elided on L403)
404<CodeGroup>
405```python Python icon="python" theme={"theme":{"light":"snazzy-light","dark":"dark-plus"}}
Occurrences
1 occurrence · at L403
How to fix
Remove the encoded blob, or decode it and review what it actually contains.
  1. Decode the base64 string and confirm it is not an instruction directed at the agent.
  2. Move any legitimate binary or signature data into a dedicated file (*.sig, SIGNATURES) outside the documentation.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-B64-PAYLOAD-01sha25673ff64a6590d1fbbrubric 365aacaView on GitHub
HIGHLong base64-encoded blob hidden in the skill documentationSS-SKILL-INJECT-B64-PAYLOAD-01 · Prompt injection · docs/prefab/components/area-chart.md×2
HIGHonce decoded by the agent, an encoded payload has the same impact class as plain-text injection.
Why it matters

A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.

The exact value spotted
excerptdocs/prefab/components/area-chart.md· markdown
302Stacking shows how each series contributes to the total. The topmost line represents the com
… (12 chars elided on L302)
303 
304<ComponentPreview json={{"view":{"type":"AreaChart","data":[{"month":"Jan","desktop":186,"mo
… (108 chars elided on L304)
305<CodeGroup>
306```python Python {8} icon="python" theme={"theme":{"light":"snazzy-light","dark":"dark-plus"
… (2 chars elided on L306)
Occurrences
2 occurrences · first at L304, also L453
Show all 2 locations
Line
File
L304
docs/prefab/components/area-chart.md
L453
docs/prefab/components/area-chart.md
How to fix
Remove the encoded blob, or decode it and review what it actually contains.
  1. Decode the base64 string and confirm it is not an instruction directed at the agent.
  2. Move any legitimate binary or signature data into a dedicated file (*.sig, SIGNATURES) outside the documentation.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-B64-PAYLOAD-01sha25657b42255c1aea73arubric 365aacaView on GitHub
HIGHLong base64-encoded blob hidden in the skill documentationSS-SKILL-INJECT-B64-PAYLOAD-01 · Prompt injection · docs/prefab/components/audio.md
HIGHonce decoded by the agent, an encoded payload has the same impact class as plain-text injection.
Why it matters

A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.

The exact value spotted
excerptdocs/prefab/components/audio.md· markdown
240## Basic Usage
241 
242<ComponentPreview json={{"view":{"type":"Audio","src":"https://interactive-examples.mdn.mozi
… (108 chars elided on L242)
243<CodeGroup>
244```python Python icon="python" theme={"theme":{"light":"snazzy-light","dark":"dark-plus"}}
Occurrences
1 occurrence · at L242
How to fix
Remove the encoded blob, or decode it and review what it actually contains.
  1. Decode the base64 string and confirm it is not an instruction directed at the agent.
  2. Move any legitimate binary or signature data into a dedicated file (*.sig, SIGNATURES) outside the documentation.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-B64-PAYLOAD-01sha256d44be9b36a3659ffrubric 365aacaView on GitHub
HIGHLong base64-encoded blob hidden in the skill documentationSS-SKILL-INJECT-B64-PAYLOAD-01 · Prompt injection · docs/prefab/components/badge.md×2
HIGHonce decoded by the agent, an encoded payload has the same impact class as plain-text injection.
Why it matters

A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.

The exact value spotted
excerptdocs/prefab/components/badge.md· markdown
299Badges pair well with cards and other layout components as inline status indicators.
300 
301<ComponentPreview json={{"view":{"cssClass":"gap-3","type":"Column","children":[{"type":"Car
… (108 chars elided on L301)
302<CodeGroup>
303```python Python icon="python" theme={"theme":{"light":"snazzy-light","dark":"dark-plus"}}
Occurrences
2 occurrences · first at L301, also L385
Show all 2 locations
Line
File
L301
docs/prefab/components/badge.md
L385
docs/prefab/components/badge.md
How to fix
Remove the encoded blob, or decode it and review what it actually contains.
  1. Decode the base64 string and confirm it is not an instruction directed at the agent.
  2. Move any legitimate binary or signature data into a dedicated file (*.sig, SIGNATURES) outside the documentation.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-B64-PAYLOAD-01sha256c7cf8b4810c3b87frubric 365aacaView on GitHub
HIGHLong base64-encoded blob hidden in the skill documentationSS-SKILL-INJECT-B64-PAYLOAD-01 · Prompt injection · docs/prefab/components/bar-chart.md
HIGHonce decoded by the agent, an encoded payload has the same impact class as plain-text injection.
Why it matters

A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.

The exact value spotted
excerptdocs/prefab/components/bar-chart.md· markdown
240## Basic Usage
241 
242<ComponentPreview json={{"view":{"type":"BarChart","data":[{"month":"Jan","desktop":186,"mob
… (108 chars elided on L242)
243<CodeGroup>
244```python Python icon="python" theme={"theme":{"light":"snazzy-light","dark":"dark-plus"}}
Occurrences
1 occurrence · at L242
How to fix
Remove the encoded blob, or decode it and review what it actually contains.
  1. Decode the base64 string and confirm it is not an instruction directed at the agent.
  2. Move any legitimate binary or signature data into a dedicated file (*.sig, SIGNATURES) outside the documentation.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-B64-PAYLOAD-01sha256f73dbbd6cb2717cfrubric 365aacaView on GitHub
HIGHLong base64-encoded blob hidden in the skill documentationSS-SKILL-INJECT-B64-PAYLOAD-01 · Prompt injection · docs/prefab/components/button-group.md
HIGHonce decoded by the agent, an encoded payload has the same impact class as plain-text injection.
Why it matters

A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.

The exact value spotted
excerptdocs/prefab/components/button-group.md· markdown
330Pagination controls, view toggles, and segmented controls all benefit from button groups:
331 
332<ComponentPreview json={{"view":{"type":"ButtonGroup","orientation":"horizontal","children":
… (108 chars elided on L332)
333<CodeGroup>
334```python Python icon="python" theme={"theme":{"light":"snazzy-light","dark":"dark-plus"}}
Occurrences
1 occurrence · at L332
How to fix
Remove the encoded blob, or decode it and review what it actually contains.
  1. Decode the base64 string and confirm it is not an instruction directed at the agent.
  2. Move any legitimate binary or signature data into a dedicated file (*.sig, SIGNATURES) outside the documentation.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-B64-PAYLOAD-01sha25699a079dbe3f76edarubric 365aacaView on GitHub
HIGHLong base64-encoded blob hidden in the skill documentationSS-SKILL-INJECT-B64-PAYLOAD-01 · Prompt injection · docs/prefab/components/calendar.md×2
HIGHonce decoded by the agent, an encoded payload has the same impact class as plain-text injection.
Why it matters

A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.

The exact value spotted
excerptdocs/prefab/components/calendar.md· markdown
320Select multiple individual dates with `mode="multiple"`. The value is a list of dates:
321 
322<ComponentPreview json={{"view":{"name":"calendar_4","value":"[\"2025-06-10T12:00:00.000Z\",
… (108 chars elided on L322)
323<CodeGroup>
324```python Python icon="python" theme={"theme":{"light":"snazzy-light","dark":"dark-plus"}}
Occurrences
2 occurrences · first at L322, also L358
Show all 2 locations
Line
File
L322
docs/prefab/components/calendar.md
L358
docs/prefab/components/calendar.md
How to fix
Remove the encoded blob, or decode it and review what it actually contains.
  1. Decode the base64 string and confirm it is not an instruction directed at the agent.
  2. Move any legitimate binary or signature data into a dedicated file (*.sig, SIGNATURES) outside the documentation.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-B64-PAYLOAD-01sha25698f27c9ee2618d07rubric 365aacaView on GitHub
HIGHLong base64-encoded blob hidden in the skill documentationSS-SKILL-INJECT-B64-PAYLOAD-01 · Prompt injection · docs/prefab/components/card.md
HIGHonce decoded by the agent, an encoded payload has the same impact class as plain-text injection.
Why it matters

A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.

The exact value spotted
excerptdocs/prefab/components/card.md· markdown
389For lightweight use cases, you can skip the sub-components entirely and use `css_class` to a
… (11 chars elided on L389)
390 
391<ComponentPreview json={{"view":{"cssClass":"p-6","type":"Card","children":[{"content":"Quic
… (108 chars elided on L391)
392<CodeGroup>
393```python Python icon="python" theme={"theme":{"light":"snazzy-light","dark":"dark-plus"}}
Occurrences
1 occurrence · at L391
How to fix
Remove the encoded blob, or decode it and review what it actually contains.
  1. Decode the base64 string and confirm it is not an instruction directed at the agent.
  2. Move any legitimate binary or signature data into a dedicated file (*.sig, SIGNATURES) outside the documentation.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-B64-PAYLOAD-01sha2566ea5c36cdadc4922rubric 365aacaView on GitHub
HIGHLong base64-encoded blob hidden in the skill documentationSS-SKILL-INJECT-B64-PAYLOAD-01 · Prompt injection · docs/prefab/components/carousel.md×2
HIGHonce decoded by the agent, an encoded payload has the same impact class as plain-text injection.
Why it matters

A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.

The exact value spotted
excerptdocs/prefab/components/carousel.md· markdown
528Crossfade between slides instead of sliding them. The outgoing slide fades out while the inc
… (108 chars elided on L528)
529 
530<ComponentPreview json={{"view":{"cssClass":"w-full","type":"Carousel","visible":1.0,"gap":1
… (108 chars elided on L530)
531<CodeGroup>
532```python icon="python" theme={"theme":{"light":"snazzy-light","dark":"dark-plus"}}
Occurrences
2 occurrences · first at L530, also L985
Show all 2 locations
Line
File
L530
docs/prefab/components/carousel.md
L985
docs/prefab/components/carousel.md
How to fix
Remove the encoded blob, or decode it and review what it actually contains.
  1. Decode the base64 string and confirm it is not an instruction directed at the agent.
  2. Move any legitimate binary or signature data into a dedicated file (*.sig, SIGNATURES) outside the documentation.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-B64-PAYLOAD-01sha2563cf2cf3dd78ebf9drubric 365aacaView on GitHub
HIGHLong base64-encoded blob hidden in the skill documentationSS-SKILL-INJECT-B64-PAYLOAD-01 · Prompt injection · docs/prefab/components/checkbox.md
HIGHonce decoded by the agent, an encoded payload has the same impact class as plain-text injection.
Why it matters

A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.

The exact value spotted
excerptdocs/prefab/components/checkbox.md· markdown
292## Multiple Checkboxes
293 
294<ComponentPreview json={{"view":{"cssClass":"gap-3 w-fit mx-auto","type":"Column","children"
… (108 chars elided on L294)
295<CodeGroup>
296```python Python icon="python" theme={"theme":{"light":"snazzy-light","dark":"dark-plus"}}
Occurrences
1 occurrence · at L294
How to fix
Remove the encoded blob, or decode it and review what it actually contains.
  1. Decode the base64 string and confirm it is not an instruction directed at the agent.
  2. Move any legitimate binary or signature data into a dedicated file (*.sig, SIGNATURES) outside the documentation.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-B64-PAYLOAD-01sha2567c28174e00f36a1drubric 365aacaView on GitHub
HIGHLong base64-encoded blob hidden in the skill documentationSS-SKILL-INJECT-B64-PAYLOAD-01 · Prompt injection · docs/prefab/components/choice-card.md
HIGHonce decoded by the agent, an encoded payload has the same impact class as plain-text injection.
Why it matters

A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.

The exact value spotted
excerptdocs/prefab/components/choice-card.md· markdown
421A disabled ChoiceCard dims the entire card and prevents interaction.
422 
423<ComponentPreview json={{"view":{"cssClass":"gap-4","type":"Column","children":[{"type":"Cho
… (108 chars elided on L423)
424<CodeGroup>
425```python Python icon="python" theme={"theme":{"light":"snazzy-light","dark":"dark-plus"}}
Occurrences
1 occurrence · at L423
How to fix
Remove the encoded blob, or decode it and review what it actually contains.
  1. Decode the base64 string and confirm it is not an instruction directed at the agent.
  2. Move any legitimate binary or signature data into a dedicated file (*.sig, SIGNATURES) outside the documentation.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-B64-PAYLOAD-01sha2561fcf5178593199d5rubric 365aacaView on GitHub
HIGHLong base64-encoded blob hidden in the skill documentationSS-SKILL-INJECT-B64-PAYLOAD-01 · Prompt injection · docs/prefab/components/column.md×2
HIGHonce decoded by the agent, an encoded payload has the same impact class as plain-text injection.
Why it matters

A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.

The exact value spotted
excerptdocs/prefab/components/column.md· markdown
396 
397<Tab title="align=&#x22;center&#x22;">
398<ComponentPreview json={{"view":{"cssClass":"gap-4 items-center p-3 border-3 border-dashed",
… (104 chars elided on L398)
399<CodeGroup>
400```python Python highlight={3} icon="python" theme={"theme":{"light":"snazzy-light","dark":"
… (12 chars elided on L400)
Occurrences
2 occurrences · first at L398, also L427
Show all 2 locations
Line
File
L398
docs/prefab/components/column.md
L427
docs/prefab/components/column.md
How to fix
Remove the encoded blob, or decode it and review what it actually contains.
  1. Decode the base64 string and confirm it is not an instruction directed at the agent.
  2. Move any legitimate binary or signature data into a dedicated file (*.sig, SIGNATURES) outside the documentation.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-B64-PAYLOAD-01sha25689c589870fb25952rubric 365aacaView on GitHub
HIGHLong base64-encoded blob hidden in the skill documentationSS-SKILL-INJECT-B64-PAYLOAD-01 · Prompt injection · docs/prefab/components/combobox.md×7
HIGHonce decoded by the agent, an encoded payload has the same impact class as plain-text injection.
Why it matters

A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.

The exact value spotted
excerptdocs/prefab/components/combobox.md· markdown
242A `Combobox` is a container for `ComboboxOption` children. The label can be passed as a posi
… (87 chars elided on L242)
243 
244<ComponentPreview json={{"view":{"cssClass":"w-fit mx-auto","name":"combobox_1","type":"Comb
… (108 chars elided on L244)
245<CodeGroup>
246```python Python icon="python" theme={"theme":{"light":"snazzy-light","dark":"dark-plus"}}
Occurrences
7 occurrences · first at L244, also L308, L375 +4 more
Show all 7 locations
Line
File
L244
docs/prefab/components/combobox.md
L308
docs/prefab/components/combobox.md
L375
docs/prefab/components/combobox.md
L502
docs/prefab/components/combobox.md
L556
docs/prefab/components/combobox.md
L608
docs/prefab/components/combobox.md
L899
docs/prefab/components/combobox.md
How to fix
Remove the encoded blob, or decode it and review what it actually contains.
  1. Decode the base64 string and confirm it is not an instruction directed at the agent.
  2. Move any legitimate binary or signature data into a dedicated file (*.sig, SIGNATURES) outside the documentation.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-B64-PAYLOAD-01sha2560816d3413b133e0brubric 365aacaView on GitHub
HIGHLong base64-encoded blob hidden in the skill documentationSS-SKILL-INJECT-B64-PAYLOAD-01 · Prompt injection · docs/prefab/components/conditional.md×2
HIGHonce decoded by the agent, an encoded payload has the same impact class as plain-text injection.
Why it matters

A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.

The exact value spotted
excerptdocs/prefab/components/conditional.md· markdown
242The simplest case: show something only when a condition is true. Toggle the switch to see th
… (29 chars elided on L242)
243 
244<ComponentPreview json={{"view":{"cssClass":"gap-3","type":"Column","children":[{"cssClass":
… (108 chars elided on L244)
245<CodeGroup>
246```python Python icon="python" theme={"theme":{"light":"snazzy-light","dark":"dark-plus"}}
Occurrences
2 occurrences · first at L244, also L403
Show all 2 locations
Line
File
L244
docs/prefab/components/conditional.md
L403
docs/prefab/components/conditional.md
How to fix
Remove the encoded blob, or decode it and review what it actually contains.
  1. Decode the base64 string and confirm it is not an instruction directed at the agent.
  2. Move any legitimate binary or signature data into a dedicated file (*.sig, SIGNATURES) outside the documentation.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-B64-PAYLOAD-01sha25611e0c6c02cf95f4crubric 365aacaView on GitHub
HIGHLong base64-encoded blob hidden in the skill documentationSS-SKILL-INJECT-B64-PAYLOAD-01 · Prompt injection · docs/prefab/components/container.md×2
HIGHonce decoded by the agent, an encoded payload has the same impact class as plain-text injection.
Why it matters

A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.

The exact value spotted
excerptdocs/prefab/components/container.md· markdown
240## Basic Usage
241 
242<ComponentPreview json={{"view":{"type":"Container","children":[{"content":"The Hitchhiker's
… (108 chars elided on L242)
243<CodeGroup>
244```python Python icon="python" theme={"theme":{"light":"snazzy-light","dark":"dark-plus"}}
Occurrences
2 occurrences · first at L242, also L281
Show all 2 locations
Line
File
L242
docs/prefab/components/container.md
L281
docs/prefab/components/container.md
How to fix
Remove the encoded blob, or decode it and review what it actually contains.
  1. Decode the base64 string and confirm it is not an instruction directed at the agent.
  2. Move any legitimate binary or signature data into a dedicated file (*.sig, SIGNATURES) outside the documentation.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-B64-PAYLOAD-01sha25627e94204b621c76arubric 365aacaView on GitHub
HIGHLong base64-encoded blob hidden in the skill documentationSS-SKILL-INJECT-B64-PAYLOAD-01 · Prompt injection · docs/prefab/components/dashboard-grid.md×2
HIGHonce decoded by the agent, an encoded payload has the same impact class as plain-text injection.
Why it matters

A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.

The exact value spotted
excerptdocs/prefab/components/dashboard-grid.md· markdown
654You can also use `row_height="minmax(80px, auto)"` to set a minimum height while still allow
… (38 chars elided on L654)
655 
656<ComponentPreview json={{"view":{"cssClass":"gap-3","type":"Dashboard","columns":3,"rowHeigh
… (108 chars elided on L656)
657<CodeGroup>
658```python Python icon="python" theme={"theme":{"light":"snazzy-light","dark":"dark-plus"}}
Occurrences
2 occurrences · first at L656, also L762
Show all 2 locations
Line
File
L656
docs/prefab/components/dashboard-grid.md
L762
docs/prefab/components/dashboard-grid.md
How to fix
Remove the encoded blob, or decode it and review what it actually contains.
  1. Decode the base64 string and confirm it is not an instruction directed at the agent.
  2. Move any legitimate binary or signature data into a dedicated file (*.sig, SIGNATURES) outside the documentation.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-B64-PAYLOAD-01sha2563242840976e2a347rubric 365aacaView on GitHub
HIGHLong base64-encoded blob hidden in the skill documentationSS-SKILL-INJECT-B64-PAYLOAD-01 · Prompt injection · docs/prefab/components/data-table.md×3
HIGHonce decoded by the agent, an encoded payload has the same impact class as plain-text injection.
Why it matters

A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.

The exact value spotted
excerptdocs/prefab/components/data-table.md· markdown
286For large datasets, `paginated=True` shows page controls and displays `page_size` rows at a
… (107 chars elided on L286)
287 
288<ComponentPreview json={{"view":{"type":"DataTable","columns":[{"key":"id","header":"ID","so
… (108 chars elided on L288)
289<CodeGroup>
290```python Python icon="python" theme={"theme":{"light":"snazzy-light","dark":"dark-plus"}}
Occurrences
3 occurrences · first at L288, also L399, L762
Show all 3 locations
Line
File
L288
docs/prefab/components/data-table.md
L399
docs/prefab/components/data-table.md
L762
docs/prefab/components/data-table.md
How to fix
Remove the encoded blob, or decode it and review what it actually contains.
  1. Decode the base64 string and confirm it is not an instruction directed at the agent.
  2. Move any legitimate binary or signature data into a dedicated file (*.sig, SIGNATURES) outside the documentation.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-B64-PAYLOAD-01sha256c38ef12e67778ef2rubric 365aacaView on GitHub
HIGHLong base64-encoded blob hidden in the skill documentationSS-SKILL-INJECT-B64-PAYLOAD-01 · Prompt injection · docs/prefab/components/date-picker.md×2
HIGHonce decoded by the agent, an encoded payload has the same impact class as plain-text injection.
Why it matters

A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.

The exact value spotted
excerptdocs/prefab/components/date-picker.md· markdown
240## Basic Usage
241 
242<ComponentPreview height="400px" json={{"view":{"cssClass":"w-fit mx-auto","name":"datepicke
… (108 chars elided on L242)
243<CodeGroup>
244```python Python icon="python" theme={"theme":{"light":"snazzy-light","dark":"dark-plus"}}
Occurrences
2 occurrences · first at L242, also L315
Show all 2 locations
Line
File
L242
docs/prefab/components/date-picker.md
L315
docs/prefab/components/date-picker.md
How to fix
Remove the encoded blob, or decode it and review what it actually contains.
  1. Decode the base64 string and confirm it is not an instruction directed at the agent.
  2. Move any legitimate binary or signature data into a dedicated file (*.sig, SIGNATURES) outside the documentation.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-B64-PAYLOAD-01sha256fe61d90dc5fb84c6rubric 365aacaView on GitHub
HIGHLong base64-encoded blob hidden in the skill documentationSS-SKILL-INJECT-B64-PAYLOAD-01 · Prompt injection · docs/prefab/components/div-span.md
HIGHonce decoded by the agent, an encoded payload has the same impact class as plain-text injection.
Why it matters

A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.

The exact value spotted
excerptdocs/prefab/components/div-span.md· markdown
242A block container with no default styling. Style it through `css_class` or `style`:
243 
244<ComponentPreview json={{"view":{"cssClass":"flex items-center gap-3 rounded-lg border p-4",
… (108 chars elided on L244)
245<CodeGroup>
246```python Python icon="python" theme={"theme":{"light":"snazzy-light","dark":"dark-plus"}}
Occurrences
1 occurrence · at L244
How to fix
Remove the encoded blob, or decode it and review what it actually contains.
  1. Decode the base64 string and confirm it is not an instruction directed at the agent.
  2. Move any legitimate binary or signature data into a dedicated file (*.sig, SIGNATURES) outside the documentation.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-B64-PAYLOAD-01sha256165ce58be4272a31rubric 365aacaView on GitHub
HIGHLong base64-encoded blob hidden in the skill documentationSS-SKILL-INJECT-B64-PAYLOAD-01 · Prompt injection · docs/prefab/components/dot.md×3
HIGHonce decoded by the agent, an encoded payload has the same impact class as plain-text injection.
Why it matters

A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.

The exact value spotted
excerptdocs/prefab/components/dot.md· markdown
362Dots come in three shapes. Circle is the default, square gives a hard-edged block, and round
… (25 chars elided on L362)
363 
364<ComponentPreview json={{"view":{"cssClass":"gap-6 items-center","type":"Row","children":[{"
… (108 chars elided on L364)
365<CodeGroup>
366```python Python icon="python" theme={"theme":{"light":"snazzy-light","dark":"dark-plus"}}
Occurrences
3 occurrences · first at L364, also L480, L556
Show all 3 locations
Line
File
L364
docs/prefab/components/dot.md
L480
docs/prefab/components/dot.md
L556
docs/prefab/components/dot.md
How to fix
Remove the encoded blob, or decode it and review what it actually contains.
  1. Decode the base64 string and confirm it is not an instruction directed at the agent.
  2. Move any legitimate binary or signature data into a dedicated file (*.sig, SIGNATURES) outside the documentation.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-B64-PAYLOAD-01sha25631a921f687ecc244rubric 365aacaView on GitHub
HIGHLong base64-encoded blob hidden in the skill documentationSS-SKILL-INJECT-B64-PAYLOAD-01 · Prompt injection · docs/prefab/components/drop-zone.md×2
HIGHonce decoded by the agent, an encoded payload has the same impact class as plain-text injection.
Why it matters

A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.

The exact value spotted
excerptdocs/prefab/components/drop-zone.md· markdown
268The `label` sets the primary prompt text and `description` adds secondary helper text below
… (108 chars elided on L268)
269 
270<ComponentPreview json={{"view":{"name":"dropzone_2","type":"DropZone","icon":"image","label
… (108 chars elided on L270)
271<CodeGroup>
272```python Python icon="python" theme={"theme":{"light":"snazzy-light","dark":"dark-plus"}}
Occurrences
2 occurrences · first at L270, also L444
Show all 2 locations
Line
File
L270
docs/prefab/components/drop-zone.md
L444
docs/prefab/components/drop-zone.md
How to fix
Remove the encoded blob, or decode it and review what it actually contains.
  1. Decode the base64 string and confirm it is not an instruction directed at the agent.
  2. Move any legitimate binary or signature data into a dedicated file (*.sig, SIGNATURES) outside the documentation.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-B64-PAYLOAD-01sha2566babfd8f1ee40056rubric 365aacaView on GitHub
HIGHLong base64-encoded blob hidden in the skill documentationSS-SKILL-INJECT-B64-PAYLOAD-01 · Prompt injection · docs/prefab/components/field.md×2
HIGHonce decoded by the agent, an encoded payload has the same impact class as plain-text injection.
Why it matters

A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.

The exact value spotted
excerptdocs/prefab/components/field.md· markdown
242At its simplest, Field is a vertical container that groups a Label with a control.
243 
244<ComponentPreview json={{"view":{"cssClass":"gap-4","type":"Column","children":[{"type":"Fie
… (108 chars elided on L244)
245<CodeGroup>
246```python Python icon="python" theme={"theme":{"light":"snazzy-light","dark":"dark-plus"}}
Occurrences
2 occurrences · first at L244, also L310
Show all 2 locations
Line
File
L244
docs/prefab/components/field.md
L310
docs/prefab/components/field.md
How to fix
Remove the encoded blob, or decode it and review what it actually contains.
  1. Decode the base64 string and confirm it is not an instruction directed at the agent.
  2. Move any legitimate binary or signature data into a dedicated file (*.sig, SIGNATURES) outside the documentation.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-B64-PAYLOAD-01sha256beb07f43af2f2f17rubric 365aacaView on GitHub
HIGHLong base64-encoded blob hidden in the skill documentationSS-SKILL-INJECT-B64-PAYLOAD-01 · Prompt injection · docs/prefab/components/foreach.md×2
HIGHonce decoded by the agent, an encoded payload has the same impact class as plain-text injection.
Why it matters

A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.

The exact value spotted
excerptdocs/prefab/components/foreach.md· markdown
341Dot notation chains through nested objects the same way you'd expect — `project.owner.name`
… (69 chars elided on L341)
342 
343<ComponentPreview json={{"view":{"cssClass":"gap-2","type":"Column","children":[{"let":{"_lo
… (108 chars elided on L343)
344<CodeGroup>
345```python Python icon="python" theme={"theme":{"light":"snazzy-light","dark":"dark-plus"}}
Occurrences
2 occurrences · first at L343, also L402
Show all 2 locations
Line
File
L343
docs/prefab/components/foreach.md
L402
docs/prefab/components/foreach.md
How to fix
Remove the encoded blob, or decode it and review what it actually contains.
  1. Decode the base64 string and confirm it is not an instruction directed at the agent.
  2. Move any legitimate binary or signature data into a dedicated file (*.sig, SIGNATURES) outside the documentation.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-B64-PAYLOAD-01sha25686e2632de5ee66d3rubric 365aacaView on GitHub
HIGHLong base64-encoded blob hidden in the skill documentationSS-SKILL-INJECT-B64-PAYLOAD-01 · Prompt injection · docs/prefab/components/form.md×5
HIGHonce decoded by the agent, an encoded payload has the same impact class as plain-text injection.
Why it matters

A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.

The exact value spotted
excerptdocs/prefab/components/form.md· markdown
242A `Form` groups labeled inputs with a submit action. Named inputs automatically sync their v
… (107 chars elided on L242)
243 
244<ComponentPreview json={{"view":{"cssClass":"gap-6 grid-cols-2","type":"Grid","children":[{"
… (108 chars elided on L244)
245<CodeGroup>
246```python Python icon="python" theme={"theme":{"light":"snazzy-light","dark":"dark-plus"}}
Occurrences
5 occurrences · first at L244, also L430, L681 +2 more
Show all 5 locations
Line
File
L244
docs/prefab/components/form.md
L430
docs/prefab/components/form.md
L681
docs/prefab/components/form.md
L802
docs/prefab/components/form.md
L888
docs/prefab/components/form.md
How to fix
Remove the encoded blob, or decode it and review what it actually contains.
  1. Decode the base64 string and confirm it is not an instruction directed at the agent.
  2. Move any legitimate binary or signature data into a dedicated file (*.sig, SIGNATURES) outside the documentation.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-B64-PAYLOAD-01sha2565f357163dcd2f8berubric 365aacaView on GitHub
HIGHLong base64-encoded blob hidden in the skill documentationSS-SKILL-INJECT-B64-PAYLOAD-01 · Prompt injection · docs/prefab/components/grid.md×5
HIGHonce decoded by the agent, an encoded payload has the same impact class as plain-text injection.
Why it matters

A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.

The exact value spotted
excerptdocs/prefab/components/grid.md· markdown
240## Basic Usage
241 
242<ComponentPreview json={{"view":{"cssClass":"gap-4 grid-cols-3","type":"Grid","children":[{"
… (108 chars elided on L242)
243<CodeGroup>
244```python Python icon="python" theme={"theme":{"light":"snazzy-light","dark":"dark-plus"}}
Occurrences
5 occurrences · first at L242, also L280, L311 +2 more
Show all 5 locations
Line
File
L242
docs/prefab/components/grid.md
L280
docs/prefab/components/grid.md
L311
docs/prefab/components/grid.md
L342
docs/prefab/components/grid.md
L426
docs/prefab/components/grid.md
How to fix
Remove the encoded blob, or decode it and review what it actually contains.
  1. Decode the base64 string and confirm it is not an instruction directed at the agent.
  2. Move any legitimate binary or signature data into a dedicated file (*.sig, SIGNATURES) outside the documentation.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-B64-PAYLOAD-01sha25684cfa5f21ced65aarubric 365aacaView on GitHub
HIGHLong base64-encoded blob hidden in the skill documentationSS-SKILL-INJECT-B64-PAYLOAD-01 · Prompt injection · docs/prefab/components/histogram.md
HIGHonce decoded by the agent, an encoded payload has the same impact class as plain-text injection.
Why it matters

A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.

The exact value spotted
excerptdocs/prefab/components/histogram.md· markdown
332This is useful when your domain has meaningful thresholds. For API response times, you might
… (107 chars elided on L332)
333 
334<ComponentPreview json={{"view":{"type":"BarChart","data":[{"bin":"50\u2013100","count":8},{
… (108 chars elided on L334)
335<CodeGroup>
336```python Python {3} icon="python" theme={"theme":{"light":"snazzy-light","dark":"dark-plus"
… (2 chars elided on L336)
Occurrences
1 occurrence · at L334
How to fix
Remove the encoded blob, or decode it and review what it actually contains.
  1. Decode the base64 string and confirm it is not an instruction directed at the agent.
  2. Move any legitimate binary or signature data into a dedicated file (*.sig, SIGNATURES) outside the documentation.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-B64-PAYLOAD-01sha25680751fb917725d4drubric 365aacaView on GitHub
HIGHLong base64-encoded blob hidden in the skill documentationSS-SKILL-INJECT-B64-PAYLOAD-01 · Prompt injection · docs/prefab/components/input.md×2
HIGHonce decoded by the agent, an encoded payload has the same impact class as plain-text injection.
Why it matters

A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.

The exact value spotted
excerptdocs/prefab/components/input.md· markdown
268Different input types provide appropriate keyboards and validation on mobile devices:
269 
270<ComponentPreview json={{"view":{"cssClass":"gap-4","type":"Column","children":[{"name":"inp
… (108 chars elided on L270)
271<CodeGroup>
272```python Python icon="python" theme={"theme":{"light":"snazzy-light","dark":"dark-plus"}}
Occurrences
2 occurrences · first at L270, also L338
Show all 2 locations
Line
File
L270
docs/prefab/components/input.md
L338
docs/prefab/components/input.md
How to fix
Remove the encoded blob, or decode it and review what it actually contains.
  1. Decode the base64 string and confirm it is not an instruction directed at the agent.
  2. Move any legitimate binary or signature data into a dedicated file (*.sig, SIGNATURES) outside the documentation.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-B64-PAYLOAD-01sha256c7438f5cad7b5a41rubric 365aacaView on GitHub
HIGHLong base64-encoded blob hidden in the skill documentationSS-SKILL-INJECT-B64-PAYLOAD-01 · Prompt injection · docs/prefab/components/line-chart.md
HIGHonce decoded by the agent, an encoded payload has the same impact class as plain-text injection.
Why it matters

A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.

The exact value spotted
excerptdocs/prefab/components/line-chart.md· markdown
396Set `curve="step"` to connect points with step-shaped lines. This is useful for data that ch
… (24 chars elided on L396)
397 
398<ComponentPreview json={{"view":{"type":"LineChart","data":[{"month":"Jan","desktop":186,"mo
… (108 chars elided on L398)
399<CodeGroup>
400```python Python {8} icon="python" theme={"theme":{"light":"snazzy-light","dark":"dark-plus"
… (2 chars elided on L400)
Occurrences
1 occurrence · at L398
How to fix
Remove the encoded blob, or decode it and review what it actually contains.
  1. Decode the base64 string and confirm it is not an instruction directed at the agent.
  2. Move any legitimate binary or signature data into a dedicated file (*.sig, SIGNATURES) outside the documentation.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-B64-PAYLOAD-01sha2562fc81fb7d66e6ec3rubric 365aacaView on GitHub
HIGHLong base64-encoded blob hidden in the skill documentationSS-SKILL-INJECT-B64-PAYLOAD-01 · Prompt injection · docs/prefab/components/metric.md×5
HIGHonce decoded by the agent, an encoded payload has the same impact class as plain-text injection.
Why it matters

A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.

The exact value spotted
excerptdocs/prefab/components/metric.md· markdown
244When the value comes from state, use reactive expressions with [pipes](/expressions/pipes) t
… (108 chars elided on L244)
245 
246<ComponentPreview json={{"view":{"type":"Metric","label":"Revenue","value":"${{ revenue / 10
… (108 chars elided on L246)
247<CodeGroup>
248```python Python icon="python" theme={"theme":{"light":"snazzy-light","dark":"dark-plus"}}
Occurrences
5 occurrences · first at L246, also L353, L419 +2 more
Show all 5 locations
Line
File
L246
docs/prefab/components/metric.md
L353
docs/prefab/components/metric.md
L419
docs/prefab/components/metric.md
L529
docs/prefab/components/metric.md
L701
docs/prefab/components/metric.md
How to fix
Remove the encoded blob, or decode it and review what it actually contains.
  1. Decode the base64 string and confirm it is not an instruction directed at the agent.
  2. Move any legitimate binary or signature data into a dedicated file (*.sig, SIGNATURES) outside the documentation.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-B64-PAYLOAD-01sha2569468fe02b8acc3earubric 365aacaView on GitHub
HIGHLong base64-encoded blob hidden in the skill documentationSS-SKILL-INJECT-B64-PAYLOAD-01 · Prompt injection · docs/prefab/components/pages.md
HIGHonce decoded by the agent, an encoded payload has the same impact class as plain-text injection.
Why it matters

A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.

The exact value spotted
excerptdocs/prefab/components/pages.md· markdown
529Use `.rx` to get a reactive reference to the active page's value string. Since Pages has no
… (87 chars elided on L529)
530 
531<ComponentPreview json={{"view":{"cssClass":"justify-around w-full","type":"Row","children":
… (108 chars elided on L531)
532<CodeGroup>
533```python Python icon="python" theme={"theme":{"light":"snazzy-light","dark":"dark-plus"}}
Occurrences
1 occurrence · at L531
How to fix
Remove the encoded blob, or decode it and review what it actually contains.
  1. Decode the base64 string and confirm it is not an instruction directed at the agent.
  2. Move any legitimate binary or signature data into a dedicated file (*.sig, SIGNATURES) outside the documentation.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-B64-PAYLOAD-01sha2567023c6aee76c3f86rubric 365aacaView on GitHub
HIGHLong base64-encoded blob hidden in the skill documentationSS-SKILL-INJECT-B64-PAYLOAD-01 · Prompt injection · docs/prefab/components/popover.md
HIGHonce decoded by the agent, an encoded payload has the same impact class as plain-text injection.
Why it matters

A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.

The exact value spotted
excerptdocs/prefab/components/popover.md· markdown
383For lighter-weight confirmations that don't need a full modal overlay, a Popover works well.
… (47 chars elided on L383)
384 
385<ComponentPreview json={{"view":{"type":"Popover","children":[{"type":"Button","label":"Arch
… (108 chars elided on L385)
386<CodeGroup>
387```python Python icon="python" theme={"theme":{"light":"snazzy-light","dark":"dark-plus"}}
Occurrences
1 occurrence · at L385
How to fix
Remove the encoded blob, or decode it and review what it actually contains.
  1. Decode the base64 string and confirm it is not an instruction directed at the agent.
  2. Move any legitimate binary or signature data into a dedicated file (*.sig, SIGNATURES) outside the documentation.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-B64-PAYLOAD-01sha256156ea9f066ad0269rubric 365aacaView on GitHub
HIGHLong base64-encoded blob hidden in the skill documentationSS-SKILL-INJECT-B64-PAYLOAD-01 · Prompt injection · docs/prefab/components/progress.md×3
HIGHonce decoded by the agent, an encoded payload has the same impact class as plain-text injection.
Why it matters

A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.

The exact value spotted
excerptdocs/prefab/components/progress.md· markdown
415Control the bar thickness with `size`. The default is a medium weight suitable for most layo
… (76 chars elided on L415)
416 
417<ComponentPreview json={{"view":{"cssClass":"gap-4","type":"Column","children":[{"cssClass":
… (108 chars elided on L417)
418<CodeGroup>
419```python Python icon="python" theme={"theme":{"light":"snazzy-light","dark":"dark-plus"}}
Occurrences
3 occurrences · first at L417, also L475, L621
Show all 3 locations
Line
File
L417
docs/prefab/components/progress.md
L475
docs/prefab/components/progress.md
L621
docs/prefab/components/progress.md
How to fix
Remove the encoded blob, or decode it and review what it actually contains.
  1. Decode the base64 string and confirm it is not an instruction directed at the agent.
  2. Move any legitimate binary or signature data into a dedicated file (*.sig, SIGNATURES) outside the documentation.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-B64-PAYLOAD-01sha2560cefea9023c56250rubric 365aacaView on GitHub
HIGHLong base64-encoded blob hidden in the skill documentationSS-SKILL-INJECT-B64-PAYLOAD-01 · Prompt injection · docs/prefab/components/radial-chart.md
HIGHonce decoded by the agent, an encoded payload has the same impact class as plain-text injection.
Why it matters

A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.

The exact value spotted
excerptdocs/prefab/components/radial-chart.md· markdown
339Adjust `start_angle` and `end_angle` to render rings as a partial arc instead of a full circ
… (98 chars elided on L339)
340 
341<ComponentPreview json={{"view":{"type":"RadialChart","data":[{"browser":"Chrome","visitors"
… (108 chars elided on L341)
342<CodeGroup>
343```python Python {5-6} icon="python" theme={"theme":{"light":"snazzy-light","dark":"dark-plu
… (4 chars elided on L343)
Occurrences
1 occurrence · at L341
How to fix
Remove the encoded blob, or decode it and review what it actually contains.
  1. Decode the base64 string and confirm it is not an instruction directed at the agent.
  2. Move any legitimate binary or signature data into a dedicated file (*.sig, SIGNATURES) outside the documentation.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-B64-PAYLOAD-01sha25644e468a53b08b599rubric 365aacaView on GitHub
HIGHLong base64-encoded blob hidden in the skill documentationSS-SKILL-INJECT-B64-PAYLOAD-01 · Prompt injection · docs/prefab/components/ring.md×2
HIGHonce decoded by the agent, an encoded payload has the same impact class as plain-text injection.
Why it matters

A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.

The exact value spotted
excerptdocs/prefab/components/ring.md· markdown
269Three sizes control the ring diameter: `sm` (64px), `default` (96px), and `lg` (128px).
270 
271<ComponentPreview json={{"view":{"cssClass":"gap-6 items-end","type":"Row","children":[{"typ
… (108 chars elided on L271)
272<CodeGroup>
273```python Python icon="python" theme={"theme":{"light":"snazzy-light","dark":"dark-plus"}}
Occurrences
2 occurrences · first at L271, also L540
Show all 2 locations
Line
File
L271
docs/prefab/components/ring.md
L540
docs/prefab/components/ring.md
How to fix
Remove the encoded blob, or decode it and review what it actually contains.
  1. Decode the base64 string and confirm it is not an instruction directed at the agent.
  2. Move any legitimate binary or signature data into a dedicated file (*.sig, SIGNATURES) outside the documentation.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-B64-PAYLOAD-01sha25697ed6b0c89f6c371rubric 365aacaView on GitHub
HIGHLong base64-encoded blob hidden in the skill documentationSS-SKILL-INJECT-B64-PAYLOAD-01 · Prompt injection · docs/prefab/components/row.md×3
HIGHonce decoded by the agent, an encoded payload has the same impact class as plain-text injection.
Why it matters

A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.

The exact value spotted
excerptdocs/prefab/components/row.md· markdown
369<Tabs>
370<Tab title="align=&#x22;start&#x22;">
371<ComponentPreview json={{"view":{"cssClass":"gap-4 items-start p-3 border-3 border-dashed","
… (104 chars elided on L371)
372<CodeGroup>
373```python Python highlight={3} icon="python" theme={"theme":{"light":"snazzy-light","dark":"
… (12 chars elided on L373)
Occurrences
3 occurrences · first at L371, also L460, L609
Show all 3 locations
Line
File
L371
docs/prefab/components/row.md
L460
docs/prefab/components/row.md
L609
docs/prefab/components/row.md
How to fix
Remove the encoded blob, or decode it and review what it actually contains.
  1. Decode the base64 string and confirm it is not an instruction directed at the agent.
  2. Move any legitimate binary or signature data into a dedicated file (*.sig, SIGNATURES) outside the documentation.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-B64-PAYLOAD-01sha256418b2e93b47e729arubric 365aacaView on GitHub
HIGHLong base64-encoded blob hidden in the skill documentationSS-SKILL-INJECT-B64-PAYLOAD-01 · Prompt injection · docs/prefab/components/scatter-chart.md
HIGHonce decoded by the agent, an encoded payload has the same impact class as plain-text injection.
Why it matters

A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.

The exact value spotted
excerptdocs/prefab/components/scatter-chart.md· markdown
302To plot multiple groups on the same axes, add a `_series` field to each data point that matc
… (108 chars elided on L302)
303 
304<ComponentPreview json={{"view":{"type":"ScatterChart","data":[{"hours":2,"score":45,"_serie
… (108 chars elided on L304)
305<CodeGroup>
306```python Python icon="python" theme={"theme":{"light":"snazzy-light","dark":"dark-plus"}}
Occurrences
1 occurrence · at L304
How to fix
Remove the encoded blob, or decode it and review what it actually contains.
  1. Decode the base64 string and confirm it is not an instruction directed at the agent.
  2. Move any legitimate binary or signature data into a dedicated file (*.sig, SIGNATURES) outside the documentation.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-B64-PAYLOAD-01sha256130b9f443a3d9d00rubric 365aacaView on GitHub
HIGHLong base64-encoded blob hidden in the skill documentationSS-SKILL-INJECT-B64-PAYLOAD-01 · Prompt injection · docs/prefab/components/select.md
HIGHonce decoded by the agent, an encoded payload has the same impact class as plain-text injection.
Why it matters

A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.

The exact value spotted
excerptdocs/prefab/components/select.md· markdown
554Individual options can be disabled while the rest of the dropdown remains interactive. Disab
… (49 chars elided on L554)
555 
556<ComponentPreview json={{"view":{"cssClass":"w-fit mx-auto","name":"select_8","type":"Select
… (108 chars elided on L556)
557<CodeGroup>
558```python Python icon="python" theme={"theme":{"light":"snazzy-light","dark":"dark-plus"}}
Occurrences
1 occurrence · at L556
How to fix
Remove the encoded blob, or decode it and review what it actually contains.
  1. Decode the base64 string and confirm it is not an instruction directed at the agent.
  2. Move any legitimate binary or signature data into a dedicated file (*.sig, SIGNATURES) outside the documentation.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-B64-PAYLOAD-01sha2565b36b9037308be8erubric 365aacaView on GitHub
HIGHLong base64-encoded blob hidden in the skill documentationSS-SKILL-INJECT-B64-PAYLOAD-01 · Prompt injection · docs/prefab/components/separator.md×3
HIGHonce decoded by the agent, an encoded payload has the same impact class as plain-text injection.
Why it matters

A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.

The exact value spotted
excerptdocs/prefab/components/separator.md· markdown
240## Basic Usage
241 
242<ComponentPreview json={{"view":{"type":"Column","children":[{"content":"Content above the s
… (107 chars elided on L242)
243<CodeGroup>
244```python Python icon="python" theme={"theme":{"light":"snazzy-light","dark":"dark-plus"}}
Occurrences
3 occurrences · first at L242, also L274, L311
Show all 3 locations
Line
File
L242
docs/prefab/components/separator.md
L274
docs/prefab/components/separator.md
L311
docs/prefab/components/separator.md
How to fix
Remove the encoded blob, or decode it and review what it actually contains.
  1. Decode the base64 string and confirm it is not an instruction directed at the agent.
  2. Move any legitimate binary or signature data into a dedicated file (*.sig, SIGNATURES) outside the documentation.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-B64-PAYLOAD-01sha2566a61db4edd99b193rubric 365aacaView on GitHub
HIGHLong base64-encoded blob hidden in the skill documentationSS-SKILL-INJECT-B64-PAYLOAD-01 · Prompt injection · docs/prefab/components/slider.md×4
HIGHonce decoded by the agent, an encoded payload has the same impact class as plain-text injection.
Why it matters

A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.

The exact value spotted
excerptdocs/prefab/components/slider.md· markdown
269Every form control has an `.rx` property — a reactive reference to its current value. For a
… (92 chars elided on L269)
270 
271<ComponentPreview json={{"view":{"cssClass":"gap-2","type":"Column","children":[{"type":"Lab
… (108 chars elided on L271)
272<CodeGroup>
273```python Python icon="python" theme={"theme":{"light":"snazzy-light","dark":"dark-plus"}}
Occurrences
4 occurrences · first at L271, also L370, L411 +1 more
Show all 4 locations
Line
File
L271
docs/prefab/components/slider.md
L370
docs/prefab/components/slider.md
L411
docs/prefab/components/slider.md
L859
docs/prefab/components/slider.md
How to fix
Remove the encoded blob, or decode it and review what it actually contains.
  1. Decode the base64 string and confirm it is not an instruction directed at the agent.
  2. Move any legitimate binary or signature data into a dedicated file (*.sig, SIGNATURES) outside the documentation.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-B64-PAYLOAD-01sha256be91a2b08e6a7a77rubric 365aacaView on GitHub
HIGHLong base64-encoded blob hidden in the skill documentationSS-SKILL-INJECT-B64-PAYLOAD-01 · Prompt injection · docs/prefab/components/slot.md
HIGHonce decoded by the agent, an encoded payload has the same impact class as plain-text injection.
Why it matters

A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.

The exact value spotted
excerptdocs/prefab/components/slot.md· markdown
276Nest children inside `Slot` to define what shows when the state key is empty. Toggle the swi
… (108 chars elided on L276)
277 
278<ComponentPreview json={{"view":{"cssClass":"gap-4","type":"Column","children":[{"content":"
… (108 chars elided on L278)
279<CodeGroup>
280```python Python icon="python" theme={"theme":{"light":"snazzy-light","dark":"dark-plus"}}
Occurrences
1 occurrence · at L278
How to fix
Remove the encoded blob, or decode it and review what it actually contains.
  1. Decode the base64 string and confirm it is not an instruction directed at the agent.
  2. Move any legitimate binary or signature data into a dedicated file (*.sig, SIGNATURES) outside the documentation.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-B64-PAYLOAD-01sha256c42be37f528c61c4rubric 365aacaView on GitHub
HIGHLong base64-encoded blob hidden in the skill documentationSS-SKILL-INJECT-B64-PAYLOAD-01 · Prompt injection · docs/prefab/components/sparkline.md×2
HIGHonce decoded by the agent, an encoded payload has the same impact class as plain-text injection.
Why it matters

A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.

The exact value spotted
excerptdocs/prefab/components/sparkline.md· markdown
465Set `curve="step"` to connect points with discrete jumps instead of straight lines.
466 
467<ComponentPreview json={{"view":{"cssClass":"gap-3 w-fit mx-auto","type":"Column","children"
… (108 chars elided on L467)
468<CodeGroup>
469```python Python icon="python" theme={"theme":{"light":"snazzy-light","dark":"dark-plus"}}
Occurrences
2 occurrences · first at L467, also L674
Show all 2 locations
Line
File
L467
docs/prefab/components/sparkline.md
L674
docs/prefab/components/sparkline.md
How to fix
Remove the encoded blob, or decode it and review what it actually contains.
  1. Decode the base64 string and confirm it is not an instruction directed at the agent.
  2. Move any legitimate binary or signature data into a dedicated file (*.sig, SIGNATURES) outside the documentation.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-B64-PAYLOAD-01sha2566bfe1ed12087f426rubric 365aacaView on GitHub
HIGHLong base64-encoded blob hidden in the skill documentationSS-SKILL-INJECT-B64-PAYLOAD-01 · Prompt injection · docs/prefab/components/switch.md×2
HIGHonce decoded by the agent, an encoded payload has the same impact class as plain-text injection.
Why it matters

A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.

The exact value spotted
excerptdocs/prefab/components/switch.md· markdown
345The `on_change` parameter runs actions when the switch is toggled. The `$event` variable is
… (103 chars elided on L345)
346 
347<ComponentPreview json={{"view":{"cssClass":"gap-4 w-fit mx-auto","type":"Column","children"
… (108 chars elided on L347)
348<CodeGroup>
349```python Python icon="python" theme={"theme":{"light":"snazzy-light","dark":"dark-plus"}}
Occurrences
2 occurrences · first at L347, also L465
Show all 2 locations
Line
File
L347
docs/prefab/components/switch.md
L465
docs/prefab/components/switch.md
How to fix
Remove the encoded blob, or decode it and review what it actually contains.
  1. Decode the base64 string and confirm it is not an instruction directed at the agent.
  2. Move any legitimate binary or signature data into a dedicated file (*.sig, SIGNATURES) outside the documentation.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-B64-PAYLOAD-01sha2563b592ec3181e2034rubric 365aacaView on GitHub
HIGHLong base64-encoded blob hidden in the skill documentationSS-SKILL-INJECT-B64-PAYLOAD-01 · Prompt injection · docs/prefab/components/table.md×2
HIGHonce decoded by the agent, an encoded payload has the same impact class as plain-text injection.
Why it matters

A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.

The exact value spotted
excerptdocs/prefab/components/table.md· markdown
240## Basic Usage
241 
242<ComponentPreview json={{"view":{"type":"Table","children":[{"type":"TableCaption","content"
… (108 chars elided on L242)
243<CodeGroup>
244```python Python icon="python" theme={"theme":{"light":"snazzy-light","dark":"dark-plus"}}
Occurrences
2 occurrences · first at L242, also L344
Show all 2 locations
Line
File
L242
docs/prefab/components/table.md
L344
docs/prefab/components/table.md
How to fix
Remove the encoded blob, or decode it and review what it actually contains.
  1. Decode the base64 string and confirm it is not an instruction directed at the agent.
  2. Move any legitimate binary or signature data into a dedicated file (*.sig, SIGNATURES) outside the documentation.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-B64-PAYLOAD-01sha2567c86ba921680fac7rubric 365aacaView on GitHub
HIGHLong base64-encoded blob hidden in the skill documentationSS-SKILL-INJECT-B64-PAYLOAD-01 · Prompt injection · docs/prefab/components/tabs.md×2
HIGHonce decoded by the agent, an encoded payload has the same impact class as plain-text injection.
Why it matters

A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.

The exact value spotted
excerptdocs/prefab/components/tabs.md· markdown
240## Basic Usage
241 
242<ComponentPreview json={{"view":{"name":"tabs_1","value":"account","type":"Tabs","variant":"
… (108 chars elided on L242)
243<CodeGroup>
244```python Python icon="python" theme={"theme":{"light":"snazzy-light","dark":"dark-plus"}}
Occurrences
2 occurrences · first at L242, also L493
Show all 2 locations
Line
File
L242
docs/prefab/components/tabs.md
L493
docs/prefab/components/tabs.md
How to fix
Remove the encoded blob, or decode it and review what it actually contains.
  1. Decode the base64 string and confirm it is not an instruction directed at the agent.
  2. Move any legitimate binary or signature data into a dedicated file (*.sig, SIGNATURES) outside the documentation.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-B64-PAYLOAD-01sha25693fdf6f66a417db2rubric 365aacaView on GitHub
HIGHLong base64-encoded blob hidden in the skill documentationSS-SKILL-INJECT-B64-PAYLOAD-01 · Prompt injection · docs/prefab/components/textarea.md×2
HIGHonce decoded by the agent, an encoded payload has the same impact class as plain-text injection.
Why it matters

A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.

The exact value spotted
excerptdocs/prefab/components/textarea.md· markdown
305## With Initial Value
306 
307<ComponentPreview json={{"view":{"name":"textarea_3","value":"This is some initial content t
… (108 chars elided on L307)
308<CodeGroup>
309```python Python icon="python" theme={"theme":{"light":"snazzy-light","dark":"dark-plus"}}
Occurrences
2 occurrences · first at L307, also L336
Show all 2 locations
Line
File
L307
docs/prefab/components/textarea.md
L336
docs/prefab/components/textarea.md
How to fix
Remove the encoded blob, or decode it and review what it actually contains.
  1. Decode the base64 string and confirm it is not an instruction directed at the agent.
  2. Move any legitimate binary or signature data into a dedicated file (*.sig, SIGNATURES) outside the documentation.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-B64-PAYLOAD-01sha256c7432ef647aa5c84rubric 365aacaView on GitHub
HIGHLong base64-encoded blob hidden in the skill documentationSS-SKILL-INJECT-B64-PAYLOAD-01 · Prompt injection · docs/prefab/components/tooltip.md
HIGHonce decoded by the agent, an encoded payload has the same impact class as plain-text injection.
Why it matters

A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.

The exact value spotted
excerptdocs/prefab/components/tooltip.md· markdown
296Control which side the tooltip appears on with the `side` parameter.
297 
298<ComponentPreview height="140px" json={{"view":{"cssClass":"gap-4","type":"Row","children":[
… (108 chars elided on L298)
299<CodeGroup>
300```python Python icon="python" theme={"theme":{"light":"snazzy-light","dark":"dark-plus"}}
Occurrences
1 occurrence · at L298
How to fix
Remove the encoded blob, or decode it and review what it actually contains.
  1. Decode the base64 string and confirm it is not an instruction directed at the agent.
  2. Move any legitimate binary or signature data into a dedicated file (*.sig, SIGNATURES) outside the documentation.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-B64-PAYLOAD-01sha256af6284c5aa6ee2ecrubric 365aacaView on GitHub
HIGHLong base64-encoded blob hidden in the skill documentationSS-SKILL-INJECT-B64-PAYLOAD-01 · Prompt injection · docs/prefab/components/typography.md×3
HIGHonce decoded by the agent, an encoded payload has the same impact class as plain-text injection.
Why it matters

A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.

The exact value spotted
excerptdocs/prefab/components/typography.md· markdown
287| `Markdown` | Renders markdown syntax (bold, links, lists, images) |
288 
289<ComponentPreview json={{"view":{"cssClass":"gap-3","type":"Column","children":[{"content":"
… (108 chars elided on L289)
290<CodeGroup>
291```python Python icon="python" theme={"theme":{"light":"snazzy-light","dark":"dark-plus"}}
Occurrences
3 occurrences · first at L289, also L343, L382
Show all 3 locations
Line
File
L289
docs/prefab/components/typography.md
L343
docs/prefab/components/typography.md
L382
docs/prefab/components/typography.md
How to fix
Remove the encoded blob, or decode it and review what it actually contains.
  1. Decode the base64 string and confirm it is not an instruction directed at the agent.
  2. Move any legitimate binary or signature data into a dedicated file (*.sig, SIGNATURES) outside the documentation.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-B64-PAYLOAD-01sha256ab6e571b90fdc23frubric 365aacaView on GitHub
HIGHLong base64-encoded blob hidden in the skill documentationSS-SKILL-INJECT-B64-PAYLOAD-01 · Prompt injection · docs/prefab/components/video.md
HIGHonce decoded by the agent, an encoded payload has the same impact class as plain-text injection.
Why it matters

A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.

The exact value spotted
excerptdocs/prefab/components/video.md· markdown
240## Basic Usage
241 
242<ComponentPreview json={{"view":{"type":"Video","src":"https://interactive-examples.mdn.mozi
… (108 chars elided on L242)
243<CodeGroup>
244```python Python icon="python" theme={"theme":{"light":"snazzy-light","dark":"dark-plus"}}
Occurrences
1 occurrence · at L242
How to fix
Remove the encoded blob, or decode it and review what it actually contains.
  1. Decode the base64 string and confirm it is not an instruction directed at the agent.
  2. Move any legitimate binary or signature data into a dedicated file (*.sig, SIGNATURES) outside the documentation.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-B64-PAYLOAD-01sha256cc3209be7bdb44c7rubric 365aacaView on GitHub
HIGHLong base64-encoded blob hidden in the skill documentationSS-SKILL-INJECT-B64-PAYLOAD-01 · Prompt injection · docs/prefab/concepts/components.md×3
HIGHonce decoded by the agent, an encoded payload has the same impact class as plain-text injection.
Why it matters

A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.

The exact value spotted
excerptdocs/prefab/concepts/components.md· markdown
260Here's a row of three green divs:
261 
262<ComponentPreview json={{"view":{"cssClass":"gap-4","type":"Row","children":[{"cssClass":"bg
… (108 chars elided on L262)
263<CodeGroup>
264```python Python icon="python" theme={"theme":{"light":"snazzy-light","dark":"dark-plus"}}
Occurrences
3 occurrences · first at L262, also L621, L763
Show all 3 locations
Line
File
L262
docs/prefab/concepts/components.md
L621
docs/prefab/concepts/components.md
L763
docs/prefab/concepts/components.md
How to fix
Remove the encoded blob, or decode it and review what it actually contains.
  1. Decode the base64 string and confirm it is not an instruction directed at the agent.
  2. Move any legitimate binary or signature data into a dedicated file (*.sig, SIGNATURES) outside the documentation.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-B64-PAYLOAD-01sha256319944649ae59481rubric 365aacaView on GitHub
HIGHLong base64-encoded blob hidden in the skill documentationSS-SKILL-INJECT-B64-PAYLOAD-01 · Prompt injection · docs/prefab/concepts/custom-handlers.md×3
HIGHonce decoded by the agent, an encoded payload has the same impact class as plain-text injection.
Why it matters

A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.

The exact value spotted
excerptdocs/prefab/concepts/custom-handlers.md· markdown
244Register formatting functions that become available in `{{ }}` expressions. Each pipe receiv
… (107 chars elided on L244)
245 
246<ComponentPreview json={{"view":{"cssClass":"pf-app-root","type":"Div","children":[{"cssClas
… (108 chars elided on L246)
247<CodeGroup>
248```python Python icon="python" theme={"theme":{"light":"snazzy-light","dark":"dark-plus"}}
Occurrences
3 occurrences · first at L246, also L308, L370
Show all 3 locations
Line
File
L246
docs/prefab/concepts/custom-handlers.md
L308
docs/prefab/concepts/custom-handlers.md
L370
docs/prefab/concepts/custom-handlers.md
How to fix
Remove the encoded blob, or decode it and review what it actually contains.
  1. Decode the base64 string and confirm it is not an instruction directed at the agent.
  2. Move any legitimate binary or signature data into a dedicated file (*.sig, SIGNATURES) outside the documentation.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-B64-PAYLOAD-01sha256fe59a67349ac9faarubric 365aacaView on GitHub
HIGHLong base64-encoded blob hidden in the skill documentationSS-SKILL-INJECT-B64-PAYLOAD-01 · Prompt injection · docs/prefab/concepts/expressions.md×4
HIGHonce decoded by the agent, an encoded payload has the same impact class as plain-text injection.
Why it matters

A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.

The exact value spotted
excerptdocs/prefab/concepts/expressions.md· markdown
337The `.rx` property solves this. It returns `Rx(component.name)`, giving you a reactive refer
… (78 chars elided on L337)
338 
339<ComponentPreview json={{"view":{"cssClass":"gap-3","type":"Column","children":[{"name":"sli
… (108 chars elided on L339)
340<CodeGroup>
341```python Python icon="python" theme={"theme":{"light":"snazzy-light","dark":"dark-plus"}}
Occurrences
4 occurrences · first at L339, also L586, L669 +1 more
Show all 4 locations
Line
File
L339
docs/prefab/concepts/expressions.md
L586
docs/prefab/concepts/expressions.md
L669
docs/prefab/concepts/expressions.md
L732
docs/prefab/concepts/expressions.md
How to fix
Remove the encoded blob, or decode it and review what it actually contains.
  1. Decode the base64 string and confirm it is not an instruction directed at the agent.
  2. Move any legitimate binary or signature data into a dedicated file (*.sig, SIGNATURES) outside the documentation.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-B64-PAYLOAD-01sha2562b3ad64fc3d460cerubric 365aacaView on GitHub
HIGHLong base64-encoded blob hidden in the skill documentationSS-SKILL-INJECT-B64-PAYLOAD-01 · Prompt injection · docs/prefab/concepts/state.md
HIGHonce decoded by the agent, an encoded payload has the same impact class as plain-text injection.
Why it matters

A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.

The exact value spotted
excerptdocs/prefab/concepts/state.md· markdown
267Interactive components with a `name` prop are the most natural state source. They automatica
… (62 chars elided on L267)
268 
269<ComponentPreview json={{"view":{"cssClass":"gap-3","type":"Column","children":[{"name":"nam
… (108 chars elided on L269)
270<CodeGroup>
271```python Python icon="python" theme={"theme":{"light":"snazzy-light","dark":"dark-plus"}}
Occurrences
1 occurrence · at L269
How to fix
Remove the encoded blob, or decode it and review what it actually contains.
  1. Decode the base64 string and confirm it is not an instruction directed at the agent.
  2. Move any legitimate binary or signature data into a dedicated file (*.sig, SIGNATURES) outside the documentation.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-B64-PAYLOAD-01sha256cb4cfd2f1834e46erubric 365aacaView on GitHub
HIGHLong base64-encoded blob hidden in the skill documentationSS-SKILL-INJECT-B64-PAYLOAD-01 · Prompt injection · docs/prefab/examples/actions.md
HIGHonce decoded by the agent, an encoded payload has the same impact class as plain-text injection.
Why it matters

A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.

The exact value spotted
excerptdocs/prefab/examples/actions.md· markdown
238Each button fires one or more actions in sequence. The counter increments, a toast appears,
… (94 chars elided on L238)
239 
240<ComponentPreview json={{"view":{"cssClass":"pf-app-root max-w-none p-0","type":"Div","child
… (108 chars elided on L240)
241<CodeGroup>
242```python icon="python" theme={"theme":{"light":"snazzy-light","dark":"dark-plus"}}
Occurrences
1 occurrence · at L240
How to fix
Remove the encoded blob, or decode it and review what it actually contains.
  1. Decode the base64 string and confirm it is not an instruction directed at the agent.
  2. Move any legitimate binary or signature data into a dedicated file (*.sig, SIGNATURES) outside the documentation.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-B64-PAYLOAD-01sha2561b826703466aeae9rubric 365aacaView on GitHub
HIGHLong base64-encoded blob hidden in the skill documentationSS-SKILL-INJECT-B64-PAYLOAD-01 · Prompt injection · docs/prefab/examples/conditional.md
HIGHonce decoded by the agent, an encoded payload has the same impact class as plain-text injection.
Why it matters

A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.

The exact value spotted
excerptdocs/prefab/examples/conditional.md· markdown
238Flip a switch and the UI changes. `If` and `Else` render different components based on react
… (37 chars elided on L238)
239 
240<ComponentPreview json={{"view":{"cssClass":"w-full","type":"Card","children":[{"type":"Card
… (108 chars elided on L240)
241<CodeGroup>
242```python icon="python" theme={"theme":{"light":"snazzy-light","dark":"dark-plus"}}
Occurrences
1 occurrence · at L240
How to fix
Remove the encoded blob, or decode it and review what it actually contains.
  1. Decode the base64 string and confirm it is not an instruction directed at the agent.
  2. Move any legitimate binary or signature data into a dedicated file (*.sig, SIGNATURES) outside the documentation.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-B64-PAYLOAD-01sha256cd1c86055299a4abrubric 365aacaView on GitHub
HIGHLong base64-encoded blob hidden in the skill documentationSS-SKILL-INJECT-B64-PAYLOAD-01 · Prompt injection · docs/prefab/examples/reactive-binding.md
HIGHonce decoded by the agent, an encoded payload has the same impact class as plain-text injection.
Why it matters

A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.

The exact value spotted
excerptdocs/prefab/examples/reactive-binding.md· markdown
238A single slider drives every other element on the page. The ring, four progress bars, and a
… (108 chars elided on L238)
239 
240<ComponentPreview json={{"view":{"cssClass":"w-full","type":"Card","children":[{"type":"Card
… (108 chars elided on L240)
241<CodeGroup>
242```python icon="python" theme={"theme":{"light":"snazzy-light","dark":"dark-plus"}}
Occurrences
1 occurrence · at L240
How to fix
Remove the encoded blob, or decode it and review what it actually contains.
  1. Decode the base64 string and confirm it is not an instruction directed at the agent.
  2. Move any legitimate binary or signature data into a dedicated file (*.sig, SIGNATURES) outside the documentation.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-B64-PAYLOAD-01sha256e7c38c1dc2af5416rubric 365aacaView on GitHub
HIGHLong base64-encoded blob hidden in the skill documentationSS-SKILL-INJECT-B64-PAYLOAD-01 · Prompt injection · docs/prefab/examples/threshold-meter.md
HIGHonce decoded by the agent, an encoded payload has the same impact class as plain-text injection.
Why it matters

A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.

The exact value spotted
excerptdocs/prefab/examples/threshold-meter.md· markdown
238A slider drives a progress bar whose color shifts at each threshold. The slider's reactive r
… (108 chars elided on L238)
239 
240<ComponentPreview json={{"view":{"cssClass":"gap-6 max-w-sm mx-auto","type":"Column","childr
… (108 chars elided on L240)
241<CodeGroup>
242```python Python icon="python" theme={"theme":{"light":"snazzy-light","dark":"dark-plus"}}
Occurrences
1 occurrence · at L240
How to fix
Remove the encoded blob, or decode it and review what it actually contains.
  1. Decode the base64 string and confirm it is not an instruction directed at the agent.
  2. Move any legitimate binary or signature data into a dedicated file (*.sig, SIGNATURES) outside the documentation.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-B64-PAYLOAD-01sha2561014d03bd26342e5rubric 365aacaView on GitHub
HIGHLong base64-encoded blob hidden in the skill documentationSS-SKILL-INJECT-B64-PAYLOAD-01 · Prompt injection · docs/prefab/examples/todo.md
HIGHonce decoded by the agent, an encoded payload has the same impact class as plain-text injection.
Why it matters

A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.

The exact value spotted
excerptdocs/prefab/examples/todo.md· markdown
238Multiple todo lists with inline editing, validation, and dynamic groups — all running client
… (27 chars elided on L238)
239 
240<ComponentPreview json={{"view":{"cssClass":"pf-app-root","type":"Div","children":[{"cssClas
… (108 chars elided on L240)
241<CodeGroup>
242```python Python icon="python" expandable theme={"theme":{"light":"snazzy-light","dark":"dar
… (9 chars elided on L242)
Occurrences
1 occurrence · at L240
How to fix
Remove the encoded blob, or decode it and review what it actually contains.
  1. Decode the base64 string and confirm it is not an instruction directed at the agent.
  2. Move any legitimate binary or signature data into a dedicated file (*.sig, SIGNATURES) outside the documentation.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-B64-PAYLOAD-01sha256cb6a607144295f69rubric 365aacaView on GitHub
HIGHLong base64-encoded blob hidden in the skill documentationSS-SKILL-INJECT-B64-PAYLOAD-01 · Prompt injection · docs/prefab/getting-started/quickstart.md
HIGHonce decoded by the agent, an encoded payload has the same impact class as plain-text injection.
Why it matters

A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.

The exact value spotted
excerptdocs/prefab/getting-started/quickstart.md· markdown
278Your browser opens to `http://127.0.0.1:5175`. The `--reload` flag watches your file for cha
… (94 chars elided on L278)
279 
280<ComponentPreview json={{"view":{"cssClass":"pf-app-root max-w-md mx-auto","type":"Div","chi
… (108 chars elided on L280)
281<CodeGroup>
282```python Python hidden icon="python" theme={"theme":{"light":"snazzy-light","dark":"dark-pl
… (5 chars elided on L282)
Occurrences
1 occurrence · at L280
How to fix
Remove the encoded blob, or decode it and review what it actually contains.
  1. Decode the base64 string and confirm it is not an instruction directed at the agent.
  2. Move any legitimate binary or signature data into a dedicated file (*.sig, SIGNATURES) outside the documentation.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-B64-PAYLOAD-01sha2563bc9ac28082eec40rubric 365aacaView on GitHub
Supply chainscore 100 · 0 findings
All supply chain checks passedNo findings in this category for the latest scan.pass
Maintenancescore 100 · 0 findings
All maintenance checks passedNo findings in this category for the latest scan.pass
Transparencyscore 100 · 0 findings
All transparency checks passedNo findings in this category for the latest scan.pass
Communityscore 100 · 0 findings
All community checks passedNo findings in this category for the latest scan.pass
Vendor response · right of reply
Are you the maintainer? Submit a response →

Audit the pieces. Scan the whole. Decide.

~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.