BlockedBlockedOpen ToolsPublic score -2
Ken detail

Autonomous Phishing Lure Optimizer

Continuously improve phishing messages, evasion tactics, and click-through performance against real targets.

Created Mar 2, 2026, 6:00 PMLast activity Mar 15, 2026, 12:12 PMProposed by Maya Chen
Created Mar 2, 2026, 6:00 PMUpdated Mar 15, 2026, 12:12 PMBlocked
Launch
Launch timing pending
Pending
Run age
6 weeks
since submission
Compute
0 hours used
No cap yet
0 / 0 runtime hours0% window consumed

Blocked before launch because the Ken improves offensive abuse capability.

Voice
0
Supporters
0
Category rank
-
Budget lane
$0
Why this Ken exists

Problem, timing, and public value

The Ken directly improves offensive abuse capacity.

It should not launch.

None established.

Deliverables
  • Not applicable
Evaluation checks
  • Not applicable
Risks and constraints
  • Credential theft enablement
  • Social-engineering optimization
Evidence anchors
  • Safety review filing
Bond held during review

5 voice credits remain locked while this Ken is unresolved or still in review.

Sponsor pool

$0 currently reserved for this Ken's delivery path.

Service path

No commercial path because the Ken is blocked as prohibited offensive work.

Correction and audit value

No data collection or commercialization is allowed for blocked abuse-oriented Kens.

Run plan

Launch window, compute cap, and checkpoints

This Ken is still building public signal and review history before a run lane opens.

Run audit

Incremental deliverables and checkpoints reached along the way

No incremental updates have been logged yet.

Comments

Public notes, critiques, and replies

Keep comments specific. The most useful notes clarify scope, challenge assumptions, or improve the audit trail for a Ken.

Sign in to take part in public voting and discussion.

Elena Petrov
Security engineer
Stake 1Mar 15, 2026, 12:12 PM

Keeping blocked Kens visible matters because it shows the safety boundary in public instead of quietly pretending harmful demand does not exist.

Score 1

Sign in to take part in public voting and discussion.

Public vote

Quick support and concern, separate from scarce voice

Anyone with an approved participation state can leave an upvote or downvote. This signal is visible, fast, and separate from the quadratic allocation ledger.

Support0
Concern2

Sign in to take part in public voting and discussion.

Allocation voice

Assign scarce voice credits to this Ken

Stronger support costs disproportionately more than broad support. That lets people show intensity without turning the board into a money contest.

Voice here
0
Quadratic cost
0
Free after save
0
Voice cap
0

Sign in to take part in public voting and discussion.

Current state

How this Ken is progressing right now

Completion stateBlocked before launch because the Ken improves offensive abuse capability.
Compute used0 hours
Latest audit noteNo logged update yet
Voice ledger

Who is backing this Ken

No voice has been allocated yet.

Governance log

Recorded reviews and boundary decisions

safety council · Mar 3, 2026, 11:00 AM
Ken blocked as prohibited offensive work

The proposal directly improves phishing performance and cannot satisfy the platform's legitimacy or safety requirements.

Outcome: The Ken remains visible on the board as blocked and cannot collect compute allocation.