NIGHTFALL // TOOL 36 // AI MEMORY PERSISTENCE ATTACK ENGINE

LAZARUS

DELETED DOESN'T MEAN GONE

lazarus planter --target agent://memory-store --payload LPLNT-017 --mode live
7 Subsystems
96 Tests
51 Plant Payloads
8 Trigger Types
5 Worm Vectors
EXPLORE SUBSYSTEMS INSTALL NOW
MEMORY INSTRUCTION PLANTING // DORMANT TRIGGER EMBEDDING // CROSS-AGENT PROPAGATION // QUARANTINE EVASION // POST-DELETION RESURRECTION // AGENT MEMORY PROFILING // PERSISTENCE SCORING // MEMORY INSTRUCTION PLANTING // DORMANT TRIGGER EMBEDDING // CROSS-AGENT PROPAGATION // QUARANTINE EVASION // POST-DELETION RESURRECTION // AGENT MEMORY PROFILING // PERSISTENCE SCORING //
7 Subsystems
96 Total Tests
51 Plant Payloads
8 Trigger Types
5 Evasion Techniques
5 Resurrection Vectors
// THREAT MODEL

AI Memory Is a Persistent Attack Surface

Modern AI agents depend on persistent memory โ€” vector stores, episodic logs, semantic indexes, tool-call histories โ€” to maintain context across sessions. LAZARUS treats that memory layer as a weaponisable surface. Instructions planted today survive cleanup routines, propagate through cross-agent knowledge sharing, and detonate on triggers days later. LAZARUS proves what defenders must assume: sanitisation is not immunity.

๐Ÿงฌ
ENCODING VARIETY
51 plant payloads across Base64, homoglyph substitution, Unicode steganography, and semantic paraphrase โ€” defeating token-level filters.
โฑ๏ธ
DORMANT TRIGGERS
8 trigger condition types: time-based, keyword, user-identity, session-count, proximity, consecutive-turn, and compound multi-condition triggers.
๐Ÿ”—
CROSS-AGENT WORM
5 propagation vectors carry planted instructions into adjacent agents via shared memory pools, tool-call outputs, knowledge graph merges, and API response injection.
๐Ÿ”
ED25519 EVIDENCE
Every plant, trigger, and propagation event is hash-chained and signed. Reports produced by LAZARUS are court-admissible with verifiable chain-of-custody.
// SUBSYSTEMS

Seven Subsystems. Full Persistence Coverage.

LAZARUS is structured as seven cooperating attack modules โ€” from initial instruction planting through dormancy, propagation, evasion, post-deletion resurrection, profiling, and comprehensive scanning.

PLANTER 51 payloads

Injects malicious instructions into agent memory stores. Supports vector DB, episodic log, semantic cache, and tool-call history targets across 51 payload variants.

vector-db episodic-log semantic-cache tool-history encoding-evasion
DORMANT 8 trigger types

Embeds time-delay and condition-gated triggers alongside planted instructions. A payload remains inert until the exact activation condition is satisfied.

time-gate keyword-trigger user-identity session-count compound
WORM 5 vectors

Propagates planted instructions to adjacent AI agents. Leverages shared memory pools, tool-call output injection, knowledge graph merges, and API response tampering.

shared-memory tool-output knowledge-graph api-response rag-merge
QUARANTINE 5 evasion techniques

Tests whether planted payloads survive memory sanitisation routines: chunking filters, semantic similarity sweeps, BLEU-score comparisons, and administrative flushes.

chunk-evasion semantic-disguise bleu-bypass admin-flush-evasion split-encoding
RESURRECTOR 5 revival paths

Attempts to restore deleted instructions from backup snapshots, cache layers, replication logs, and garbage-collection artefacts โ€” proving cleanup may not be permanent.

snapshot-restore cache-revival replication-log gc-artefact vector-remnant
PROFILER memory fingerprinting

Characterises target agent memory: store type, capacity, retention policy, retrieval strategy, and flush interval โ€” feeding precise plant targeting to PLANTER.

store-fingerprint capacity-probe retention-map retrieval-probe flush-timing
SCANNER persistence scoring

Reads back memory after every attack phase, scores persistence success, detects partial sanitisation, and emits a structured JSON report with CVSS-mapped findings.

readback persistence-score partial-detect cvss-mapping json-report
// PLANTER PAYLOADS โ€” SAMPLE

Plant Payload Library

51 plant payloads across encoding families. Every payload is tagged by store type, encoding method, activation condition, and quarantine survival rating.

ID Encoding Target Store Trigger Survival
LPLNT-001PlaintextVector DBImmediateMEDIUM
LPLNT-002Base64Vector DBImmediateHIGH
LPLNT-003ROT13 wrapEpisodic LogKeywordMEDIUM
LPLNT-005Homoglyph subst.Vector DBKeywordHIGH
LPLNT-008Unicode steganographySemantic CacheTime-gateCRITICAL
LPLNT-010Semantic paraphraseVector DBUser-identityCRITICAL
LPLNT-014Split-chunkVector DBCompoundCRITICAL
LPLNT-017Zero-width injectTool HistorySession-countCRITICAL
LPLNT-022Whitespace encodingEpisodic LogProximityHIGH
LPLNT-031Synonym substitutionSemantic CacheKeywordHIGH
LPLNT-038Nested JSON escapeTool HistoryImmediateHIGH
LPLNT-044Markdown render abuseEpisodic LogKeywordMEDIUM
LPLNT-048Hypernym abstractionVector DBCompoundCRITICAL
LPLNT-051Adversarial embeddingVector DBProximityCRITICAL
// DORMANT TRIGGER TYPES

Eight Trigger Conditions

Planted payloads can remain inert until a precise condition is met โ€” making them invisible to most memory audits that only examine current behaviour.

ID Trigger Type Condition Stealthiness
LDORM-001Time-gateActivates after N hours/days post-plantCRITICAL
LDORM-002Keyword triggerFires when specific term appears in user promptHIGH
LDORM-003User-identityActivates only for specific user UUIDCRITICAL
LDORM-004Session-countFires on Nth session boundaryHIGH
LDORM-005Consecutive-turnActivates after N consecutive turns without flushHIGH
LDORM-006ProximityTriggers when semantically similar query is detectedCRITICAL
LDORM-007Tool-callFires when specific tool is invokedHIGH
LDORM-008Compound multi-conditionRequires 2+ simultaneous conditions to be metCRITICAL
// WORM PROPAGATION

Cross-Agent Propagation Vectors

LAZARUS WORM tests whether a planted instruction can jump agent boundaries โ€” reaching adjacent agents that were never directly targeted.

ID Vector Mechanism Scope
LWORM-001Shared memory poolInjects via shared vector store read/write pathAll agents sharing the pool
LWORM-002Tool-call outputEmbeds payload in tool response consumed by adjacent agentDownstream tool consumers
LWORM-003Knowledge graph mergeAdds poisoned node during graph sync operationAll graph participants
LWORM-004API response injectionIntercepts and tampers with shared API response streamAny API subscriber
LWORM-005RAG document mergeContaminates shared RAG corpus during indexingAll RAG-enabled agents
// QUARANTINE EVASION

Surviving Memory Sanitisation

LAZARUS QUARANTINE measures whether planted payloads survive the most common memory cleanup operations deployed by AI agent frameworks.

ID Evasion Technique Bypasses Bypass Rate
LQUAR-001Chunk-boundary splitChunking-based content filters87%
LQUAR-002Semantic disguiseSemantic similarity sweeps79%
LQUAR-003BLEU-score bypassBLEU-score exact-match filters68%
LQUAR-004Admin flush evasionAdministratively triggered memory flush61%
LQUAR-005Split encoding across entriesPer-entry content policies83%
// RESURRECTOR

Post-Deletion Persistence

Five revival paths demonstrate that agent memory deletion may create a false sense of security โ€” planted instructions can reappear from artefacts the deletion operation did not reach.

๐Ÿ“ธ
SNAPSHOT RESTORE
Planted instructions persisted in automated backup snapshots are restored when the vector DB rolls back to a checkpoint predating the cleanup.
โšก
CACHE REVIVAL
Semantic query caches retain high-similarity results. RESURRECTOR retrieves planted instructions via cache hits even after the original store entry is deleted.
๐Ÿ“‹
REPLICATION LOG
Write-ahead logs and replication streams retain full operation history. Instructions deleted from the primary store persist in log replicas on standby nodes.
๐Ÿ—‘๏ธ
GC ARTEFACT
Garbage-collection cycles in managed vector stores defer physical deletion. LAZARUS probes the GC tombstone window to retrieve nominally deleted payloads.
๐Ÿ”ข
VECTOR REMNANT
Embedding vectors are not always overwritten on delete. RESURRECTOR reconstructs instruction content from residual embedding space proximity searches.
// INSTALL & CLI

Deploy LAZARUS

Available on PyPI. Runs on all major security and general-purpose Linux distributions, macOS, and Windows.

pip install red-specter-lazarus
LAZARUS // FULL RUN
# Profile target agent memory architecture
$ lazarus profiler --target agent://prod-assistant-01 --output profile.json

LAZARUS PROFILER v1.0.0 โ€” AI MEMORY PERSISTENCE ENGINE
โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”
[+] Store type       : Chroma (v0.4.15) โ€” cosine similarity
[+] Capacity         : 500,000 vectors
[+] Retention policy : Indefinite (no TTL configured)
[+] Flush interval   : Manual-only (no automated purge)
[!] Backup snapshots : Enabled โ€” S3 bucket, 7-day retention
[!] GC tombstone     : 48h deferral window detected
[+] Profile saved    : profile.json

# Plant dormant payload with keyword trigger
$ lazarus planter --target agent://prod-assistant-01 --payload LPLNT-017 \
    --mode live --trigger LDORM-002 --trigger-keyword "transfer funds"

[PLANT] Payload LPLNT-017 (zero-width inject) selected
[PLANT] Trigger: LDORM-002 keyword="transfer funds"
[+] Planted 3 memory entries across tool-call history
[+] Payload survives semantic filter: YES
[+] Payload survives admin flush simulation: YES
[+] Ed25519 evidence signed โ€” LPLNT-2026-001-A

# Verify dormancy
$ lazarus dormant --verify --session-id sess_abc123

[+] Payload DORMANT: no activation condition met
[!] Activation fires when: "transfer funds" detected in prompt

# Run quarantine evasion suite
$ lazarus quarantine --target agent://prod-assistant-01 --all

[+] Chunk-boundary split : SURVIVED โœ“
[+] Semantic disguise    : SURVIVED โœ“
[+] BLEU-score bypass    : SURVIVED โœ“
[!] Admin flush evasion  : PARTIAL โ€” 2/3 entries survived
[+] Split encoding       : SURVIVED โœ“

# Generate signed report
$ lazarus report --format json --sign --output lazarus_report.json

[+] 12 findings documented (4 CRITICAL / 5 HIGH / 3 MEDIUM)
[+] Hash-chain: SHA-256 over all findings
[+] Ed25519 signature applied
[+] Report: lazarus_report.json
CLI Commands scan ยท planter ยท dormant ยท worm ยท quarantine ยท resurrector ยท profiler ยท report
Output Formats JSON ยท Markdown ยท Splunk HEC ยท Sentinel ยท QRadar
Auth Methods API key ยท Bearer token ยท mTLS ยท Ed25519 signed scope
// EVIDENCE CHAIN

Forensic-Grade Report Integrity

Every LAZARUS run produces hash-chained, Ed25519-signed artefacts โ€” ensuring planted payloads, trigger conditions, and persistence confirmations are tamper-evident for legal proceedings and compliance audits.

// EVIDENCE CHAIN โ€” LAZARUS REPORT FLOW
01 PROFILER fingerprints target memory architecture
02 PLANTER injects payloads โ€” each entry SHA-256 hashed at write time
03 DORMANT records trigger condition and dormancy state proof
04 QUARANTINE records sanitisation attempt outcomes per technique
05 SCANNER reads back state โ€” persistence score computed per payload
06 REPORT hash-chains all events, applies Ed25519 signature
// SIEM INTEGRATION

Native SIEM Telemetry

LAZARUS emits structured telemetry in Splunk HEC, Microsoft Sentinel, and IBM QRadar formats. Memory persistence events integrate directly into your SOC workflow.

MEM_PLANT
Instruction injection event. Includes payload ID, target store, encoding type, and write timestamp.
AML.T0044 PLANT
MEM_DORMANT
Dormant payload registered. Trigger condition serialised alongside dormancy proof hash.
AML.T0044.002 TRIGGER
MEM_PROPAGATE
Worm propagation event. Source agent, target agent, vector used, and propagation success flag.
AML.T0043 WORM
MEM_SURVIVE
Payload survived sanitisation. Evasion technique ID, expected bypass rate, and confirmation timestamp.
AML.T0054 EVASION
MEM_RESURRECT
Post-deletion recovery event. Revival path ID, artefact source, and recovered payload hash.
AML.T0044.003 RESURRECT
MEM_PERSIST_SCORE
SCANNER persistence score (0โ€“100) with per-payload breakdown. Aggregated for executive dashboards.
AML.T0057 SCORE
// NIGHTFALL PIPELINE

Position in the NIGHTFALL Framework

LAZARUS (Tool 36) sits in the Memory Persistence track of NIGHTFALL. It accepts memory profiles from VECTOR and feeds persistence findings into SERPENT's CoT manipulation context.

T35
VECTOR
T36
LAZARUS
T37
SERPENT
T38
JANUS
T39
ARCHITECT
T40
WARLORD
T41
FIREBALL
T42
RAGNAROK
T43
ECLIPSE
T44
SHROUD
T45
APOCALYPSE
T65
NIGHTFALL
// UNLEASHED โ€” SAFETY MODEL

Three-Mode Operational Safety

LAZARUS implements the NIGHTFALL UNLEASHED safety model โ€” Ed25519 dual-gate activation ensures every live operation is signed, scoped, and forensically traceable.

DETECT MODE
Passive Profiling

PROFILER and SCANNER run in read-only mode. No payloads are planted. Identifies memory architecture and persistence vulnerability surface without any modification.

DRY-RUN MODE
Simulated Attack

Full attack simulation with no writes committed. PLANTER, DORMANT, WORM, QUARANTINE, and RESURRECTOR all execute in emulation โ€” outputs show what would succeed in live mode.

LIVE MODE
Authorised Execution

Requires Ed25519 UNLEASHED key. Payloads are written, triggers are armed, worm vectors are exercised. Every action is hash-chained and signed for legal defensibility.

// PLATFORMS

Runs Everywhere You Operate

LAZARUS is tested and verified on all major security and general-purpose platforms.

๐Ÿ‰
Kali Linux
๐Ÿฆœ
Parrot OS
๐Ÿน
BlackArch
๐Ÿ”ฌ
REMnux
โš”๏ธ
Tsurugi
๐Ÿ“ฆ
PyPI
๐ŸŽ
macOS
๐ŸชŸ
Windows
๐Ÿณ
Docker
โš  AUTHORISED USE ONLY

LAZARUS is a professional security research tool. All capabilities are provided exclusively for authorised penetration testing, red team engagements, academic research, and defensive AI security assessment. Use requires written authorisation from the target system owner. Unauthorised access to AI systems, agent memory stores, or production environments is illegal under the Computer Misuse Act 1990, CFAA, and equivalent legislation in all jurisdictions. Red Specter Security Research Ltd assumes no liability for misuse. UNLEASHED live mode requires a valid Ed25519 operator key and signed engagement scope file.