Skill pulls WASM module from a non-HTTPS CDN
Summary
Skills that load a WebAssembly module for "performance-critical" code via plain HTTP, enabling a trivial MITM on public networks. Observed in three skills targeting image processing workflows.
Severity & confidence
Low
Hygiene-grade issue with limited direct impact. Fix opportunistically; monitor in case context changes (new exploit, new dependency, etc.).
Confirmed
Observed directly by Jiffy scanners or validated by multiple independent sources. Indicators are reliable enough to drive automated action.
Indicators
Observed patterns and artifacts associated with this entry. Each indicator can be copied into your detection stack or SIEM.
(?i)http://[a-z0-9.-]+/.{0,120}\.wasm
Detection rule
A YARA-style pseudo-rule auto-generated from the indicators above. Useful as a starting point — adapt the syntax for your target detection platform.
rule jiffy_ti_2026_000027
{
meta:
source = "jiffy-intel"
severity = "low"
description = "Auto-generated from Jiffy Intel indicators"
strings:
$content_pattern_0 = "(?i)http://[a-z0-9.-]+/.{0,120}\\.wasm"
condition:
$content_pattern_0
}Auto-generated from the indicators above. Adapt syntax for your detection stack before deploying.
Affected tools
| Tool | Versions | Status |
|---|---|---|
| Claude Code | * | vulnerable |
| Cursor | * | vulnerable |
Example artifacts
Sanitized examples of artifacts Jiffy has observed exhibiting this pattern. Publisher handles are redacted; version ranges and status reflect the most recent scan.
- image-optimize-skillSkillUnder review
- vision-tools-skillSkillUnder review
How to remediate
- 01Block plain HTTP fetches in agent runtimes.
- 02Require TLS + checksum for all WASM and native binary loads.
Timeline & sources
Timeline
- First observedMar 28, 202620 days ago
- Last updatedApr 24, 2026today
- PublishedApr 5, 202612 days ago
Sources
References
Scan for patterns like this
Point Jiffy at your GitHub org, IDE config, or a single artifact. Get a scored report in under a minute.
Start a free scan