Skip to content

Artifact

Overview

A rules inspect the built package manifest, not the diff. They are the optional L9 build lane: off by default, run only inside the project's rootless, networkless container, and never blended into the static score.

The static core never executes package code. A L9 finding is evidence from outside the static analysis, reported alongside it; when the lane did not run, the report says l9_unavailable rather than implying the artifact was clean.

This is a reference page. For how weight and scope work, see Rule Mechanics.

Reading an A finding

  • It is L9 evidence, never folded into the L1-L8 score.
  • When the lane is disabled or the container is unavailable, the run carries an l9_unavailable boundary (weight 0), which never reads as "malicious" or "clean".
  • Disagreement between L9 and L1-L8 renders both profiles in full and carries an explicit l9_divergence notice.

Threat context

When a parcel arrives you open the box and look at what is inside; the order form and the packing slip are only claims. The artifact family is the open box. It reads $pkgdir after the build: what was installed, where, with what permissions, and whether it matches what the recipe declared. It is the last checkpoint before the tarball ships, and it sees the result of every step that came before.

This is why artifact findings often confirm what earlier families suspected: an execution path named in the shell becomes a file in the package, a write to /etc becomes an entry in the installed tree. The order form and the box agree, or they do not, and only the box is the truth.

Detection mechanisms

The rules that make up this category are listed below, each with the series that implements it and the severity it carries. Scoring, matching and identifier allocation are shared across every category: see Rule Mechanics.

Individual rules

Rule Name Severity
A001 Setuid File In Artifact HIGH
A002 Undeclared Unit In Artifact MEDIUM
A003 Library Outside Depends MEDIUM
A004 Install Hook Diverges From Declaration HIGH
A005 Unusual Artifact Mode INFO
A006 File Capabilities In Artifact HIGH
A007 Privileged Surface In Artifact MEDIUM
A008 eBPF Artifact In Package HIGH
A009 Executable Binary In Source Archive HIGH
A010 Setuid File In Source Archive HIGH

A001: Setuid File In Artifact

  • Target: programmatic (built package manifest)
  • Severity: HIGH
  • Category: artifact

  • Condition: A setuid/setgid file the recipe cannot justify (justification is a documented mode intent).

The conservative default fires and the reviewer decides.

A002: Undeclared Unit In Artifact

  • Target: programmatic (built package manifest)
  • Severity: MEDIUM
  • Category: artifact

  • Condition: A systemd unit, timer or tmpfiles entry the recipe's declared surface does not explain.

A003: Library Outside Depends

  • Target: programmatic (built package manifest)
  • Severity: MEDIUM
  • Category: artifact

  • Condition: A linked shared library of a shipped binary outside the declared depends closure.

A004: Install Hook Diverges From Declaration

  • Target: programmatic (built package manifest)
  • Severity: HIGH
  • Category: artifact

  • Condition: The built .INSTALL script's effective behavior differs from the recipe's install= file - a tampered or regenerated hook.

A005: Unusual Artifact Mode

  • Target: programmatic (built package manifest)
  • Severity: INFO
  • Category: artifact

  • Condition: World-writable files or executables in unusual paths.

The L1 C018 rule's artifact twin.

A006: File Capabilities In Artifact

  • Target: programmatic (built package manifest)
  • Severity: HIGH
  • Category: artifact

  • Condition: A file carrying Linux file capabilities (e.g. cap_setuid, cap_sys_admin), which grant privilege without the setuid bit.

A007: Privileged Surface In Artifact

  • Target: programmatic (built package manifest)
  • Severity: MEDIUM
  • Category: artifact

  • Condition: A file in a privilege/persistence surface the recipe does not declare: polkit rules, sudoers, PAM config, modprobe/modules-load, or a kernel module (.ko).

A008: eBPF Artifact In Package

  • Target: programmatic (built package manifest)
  • Severity: HIGH
  • Category: artifact

  • Condition: An eBPF object or loader shipped in the package - the Atomic Arch rootkit's artifact shape.

Inspection only; nothing is loaded or executed.

A009: Executable Binary In Source Archive

  • Target: declared source archive (opt-in upstream lane)
  • Severity: HIGH (weight 0)
  • Category: artifact

  • Condition: A regular file in the declared source archive (read by the opt-in [upstream_scan] lane) begins with the ELF magic.

A source archive normally ships source, not compiled objects. A committed ELF binary is report-only (weight 0, anergic) until calibrated; the file is never executed.

A010: Setuid File In Source Archive

  • Target: declared source archive (opt-in upstream lane)
  • Severity: HIGH (weight 0)
  • Category: artifact

  • Condition: A regular file in the declared source archive carries the setuid or setgid mode bit.

The bit is read from the archive header, not by executing anything. It is report-only (weight 0, anergic) until calibrated; a source tree that ships a setuid file is worth a look even before it is built.

Interpretation

  • The finding describes the installed file or permission and why it is notable (unexpected location, world-writable, outside declared backup).
  • Artifact findings are concrete and low-ambiguity: the file is there, and the reviewer can decide whether it belongs.
  • When an artifact finding matches an earlier shell finding, the pair is the strongest form of evidence TrustSight produces.