Versioned security assessment

Report ID: SA-A49C6748

7/7/2026, 1:56:58 AM

memory-forensics security assessment v3

Skill Security Certification Report

Audit History
Audit model: codex Historical report
Skill name
memory-forensics
Version
v3
Maintainer
sickn33
Coverage
1 Files scanned · 492 Lines analyzed
Policy version
Unavailable

Highest confirmed finding severity

High

1 confirmed security finding requires attention.

Installation context

Historical evidence

This report may not describe the currently installable artifact. Open the current Skill page for install guidance.

Open current Skill page

This report does not block or authorize the manifest or ZIP.

Most command-related findings are false positives caused by Markdown code fences in a documentation-only forensic guide. Confirmed risks remain for privileged live memory acquisition, raw /dev and /proc memory access, process memory dumping, and credential extraction guidance.

Report position

Historical report

Open audit history before using this report to install.

Audit attestation

Not attestable

The required immutable binding is incomplete.

Human verification

Not verified

No human verification is recorded for this report.

Coverage

1 Files scanned · 492 Lines analyzed

12 items shown for review

Limitations

This report does not claim runtime or sandbox execution and does not prove the absence of side effects.

Evidence chain

Follow the evidence from source binding to the install contract. Available evidence supports verification; it is not a safety guarantee.

  1. Source

    Binding unavailable

  2. Artifact

    Identity incomplete

  3. Audit

    Complete

  4. Install contract

    Open manifest to verify

    Open manifest

Capabilities observed

Observed means this report recorded supporting evidence. Not recorded does not prove that a capability is absent.

Contains scripts

May execute code included with the Skill.

Not recorded by this audit

Network access

May connect to external services.

Observed in 1 evidence location

Filesystem access

May read or write local files.

Observed in 7 evidence locations

Env variables

May read values from the process environment.

Not recorded by this audit

External commands

May invoke commands or programs outside the Skill.

Observed in 53 evidence locations

Capability review items (11)
High
sudo privilege escalation
sudo insmod lime.ko "path=/tmp/memory.lime format=lime"
The documented command uses sudo to load a kernel memory acquisition module and write a RAM image. That is privileged live-system access that can expose secrets and affect host stability.
High
sudo privilege escalation
sudo dd if=/dev/mem of=memory.raw bs=1M
The documented command uses sudo to read /dev/mem into a raw memory image. This directly accesses sensitive physical memory and can disclose credentials or private data.
High
sudo privilege escalation
sudo cp /proc/kcore memory.elf
The documented command uses sudo to copy /proc/kcore into an ELF memory image. That provides privileged access to kernel memory and can disclose sensitive host data.
High
sudo privilege escalation
sudo ./osxpmem -o memory.raw
The documented macOS acquisition command runs a memory capture tool with sudo. Live privileged memory capture can expose secrets and should require explicit authorization.
High
Linux /proc filesystem access
# /proc/kcore (ELF format)
The section introduces /proc/kcore as a memory acquisition source. Accessing that interface is privileged kernel memory access with sensitive data exposure risk.
High
Linux /proc filesystem access
sudo cp /proc/kcore memory.elf
The command copies /proc/kcore to a memory image using sudo. This can expose kernel memory and credentials from a live system.
High
Non-standard device file access
# /dev/mem (limited, requires permissions)
The section recommends /dev/mem as a live memory acquisition source. That device exposes raw physical memory and should be treated as high-risk.
High
Non-standard device file access
sudo dd if=/dev/mem of=memory.raw bs=1M
The command reads directly from /dev/mem into a raw image. Direct physical memory access can disclose secrets and may destabilize the host.
High
Memory-mapped file access
vol -f memory.raw windows.memmap --pid <PID> --dump
The command dumps process memory from a RAM image by PID. Process memory can contain credentials, tokens, private data, and malware artifacts.
High
Memory-mapped file access
vol -f memory.raw windows.memmap --pid 1234 --dump
The command dumps process memory for a specific PID from an image. This is legitimate forensic work but can expose sensitive runtime data.
Medium
Temp directory access
sudo insmod lime.ko "path=/tmp/memory.lime format=lime"
The acquisition example writes a full memory image under /tmp. Temporary directories can have weaker handling controls for highly sensitive RAM captures.

Risk findings

Confirmed security concerns are separated from items that still need review.

Confirmed security concerns (1)

RISK-001 High
Credential Extraction Guidance
The skill documents hashdump, lsadump, cachedump, and Mimikatz-style credential extraction from memory. This is valid for authorized forensics but can also support credential theft if misused.
The credential extraction section explicitly lists memory plugins for hashes, LSA secrets, cached domain credentials, and Mimikatz-style extraction.

Remediation

Suggested fixes recorded by this audit. Applying them is the maintainer’s responsibility.

  1. FIX-001
    High
    Privileged live memory acquisition commands are shown without strong authorization warnings.
    Add explicit authorization, production-impact, and evidence-handling warnings before sudo, /dev/mem, /proc/kcore, and live capture examples.
  2. FIX-002
    High
    Credential extraction workflows can expose password hashes, LSA secrets, and cached credentials.
    Frame credential extraction as authorized incident response only and include handling rules for secrets in outputs and reports.
  3. FIX-003
    High
    Process memory dump examples do not warn that extracted dumps can contain sensitive user or application data.
    Add guidance to minimize access, redact secrets, and store extracted process memory under approved evidence controls.
  4. FIX-004
    Medium
    A full memory image is written to /tmp in the LiME example.
    Recommend a controlled evidence directory with restrictive permissions, encryption at rest, and immediate hashing.

Expert evidence

Immutable subject identity, scanner metadata, dismissed matches, and source-level evidence.

Artifact subject

Marketplace commit
Unavailable
Content hash
Unavailable
Tree hash
Unavailable
Skill path
Unavailable
Audit payload hash
Unavailable

Analysis metadata

Audit model: codex

Analysis state: Complete

Scope is limited to the recorded files, lines, methods, and evidence. No runtime or sandbox execution is claimed.

Static false positives ignored (2)
Critical
Cobalt Strike keywords
description = "Detects Cobalt Strike beacon in memory"
Force-confirmed blocker/critical static finding; AI dismissal overridden.
High
Malware type keywords
### Rootkit Detection
Force-confirmed blocker/high static finding; AI dismissal overridden.

Verify and export

The manifest and lockfile bind install artifacts to cryptographic hashes. This integrity claim is separate from the security assessment.

Audit attestation: not_attestable