Versioned security assessment

Report ID: SA-13882F00

6/30/2026, 5:04:08 PM

memory-forensics security assessment v2

Skill Security Certification Report

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

Highest confirmed finding severity

High

2 confirmed security findings require 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.

The static external-command findings are mostly markdown examples for forensic tools, not hidden code execution. However, the skill gives dual-use guidance for privileged live memory acquisition and credential extraction from memory, so it should not be published without additional review and safeguards.

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

6 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 3 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 5 evidence locations

Capability review items (4)
High
Privileged Live Memory Acquisition Commands
The skill includes examples that load a kernel module, read /dev/mem, copy /proc/kcore, and run osxpmem with sudo. These are legitimate forensic techniques, but they require elevated access and can expose full system memory or affect a live host if misused.
The commands are explicit and require privileged access to live memory sources. The surrounding context is forensic acquisition, so the risk is dual-use rather than confirmed malicious.
Medium
Process Memory and File Dumping Workflows
Several examples dump process memory, suspicious executables, registry hives, and files from captured memory. This is normal memory forensics behavior, but dumped artifacts can contain secrets, private data, or malware samples.
The commands directly dump memory and artifacts. The risk is credible, but the examples are standard defensive forensic procedures.
Medium
Network and System Reconnaissance of Memory Images
The skill includes commands to enumerate processes, network connections, modules, mounts, environment variables, and command lines from memory images. These are expected forensic tasks, but they can reveal sensitive host and user data.
The commands clearly enumerate sensitive state from memory. They operate on memory captures rather than scanning third-party systems, which lowers the severity.
Low
Markdown Code Fences Flagged as Ruby Backticks
Many static external-command findings come from markdown code fences such as powershell, bash, c, python, and yara. These are examples in documentation, not executable Ruby backtick calls in code.
The flagged characters delimit markdown examples. There is no Ruby source file or executable wrapper in the skill.

Risk findings

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

Confirmed security concerns (2)

RISK-001 High
Credential Extraction From Memory
The skill documents hashdump, lsadump, cachedump, and Mimikatz-style credential extraction from memory. These commands can support incident response, but they can also enable credential theft if used without authorization.
The section is clearly about extracting hashes, LSA secrets, and cached credentials. The document frames this as forensic analysis, but the misuse potential is direct and high.
RISK-002 Medium
Offensive Tooling References Used for Detection
The skill references process injection, rootkit behavior, shellcode patterns, and a Cobalt Strike YARA rule. These references are presented as detection content, so the Cobalt Strike static blocker appears to be contextual rather than malicious.
The static keywords are present, but the surrounding text consistently describes detection and analysis. I did not find evidence of payload generation, deployment, or evasion instructions.

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 (1)
Low
Hardcoded URL Is Documentation
The hardcoded URL points to the Volatility symbol download location in a comment. It is not used for data exfiltration or automatic network access.
The URL appears only in an installation note. No command sends local data to that URL.

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