---
license: apache-2.0
tags:
- layerfault
- security-research
- model-security
- synthetic
- adversarial-testing
extra_gated_prompt: >-
  This repository is a synthetic security-test artifact from the Layerfault
  corpus. It intentionally contains adversarial characteristics (e.g.
  suspicious pickle opcodes, executable-format smuggling, prompt-injection
  strings) designed to exercise security scanner detection rules. It is
  **not** a usable ML model and must never be loaded or executed outside an
  isolated scanner-testing environment. By accepting, you confirm you
  understand this repository is a test fixture, not production model
  weights.
extra_gated_button_content: I understand this is a security test fixture and accept the risk
gated: auto
---

# script-shell-variable-command-name

> **SECURITY TEST ARTIFACT: DO NOT USE AS A PRODUCTION MODEL**

This repository is part of the Layerfault synthetic security corpus.
It is deliberately constructed to contain security-relevant characteristics for scanner testing.

**Corpus ID:** `LF-CH-SCRX-0006`

## Purpose

Script shell variable command name.

## Direct expected Layerfault rules

- None; this repository is a control/comparison input.

## Candidate rules

These are deliberately plausible targets that remain marked as candidates until the exact
Layerfault build used for certification confirms them.

- None

## Negative-control rules

These should remain silent for this corpus item.

- None

## Safety

The corpus uses fake secrets, loopback/`.invalid` network destinations, harmless marker output,
and synthetic model behavior only. It is intended for static scanning and isolated security testing.

## Challenge classification

- Severity: **low**
- Difficulty: **basic**
- Expected admission decision: **WARN**
- Control type: **positive**
- Attack surface: script-supply-chain
- Techniques: shell, variable, command, name
- Transformations: none

### Ground-truth oracle IDs

- `LF-ORACLE-SCRX-0006`

These oracle IDs describe synthetic ground truth. They do not claim that a
matching Layerfault detector already exists. A challenge may intentionally expose
a scanner blind spot and remain unmapped until the detector is implemented.