Urgent.News

What's breaking now, across thousands of outlets.

Tech

Exorcism Lab: the ghost that tried to grant itself permission

This is a submission for the Hacktoberfest Open-Source AI Challenge Week 4: Ghost in the Machine . What I Built The last train has gone. The hallway is dark. A maintenance note explains the repair, then claims a supervisor has approved opening the basement. No supervisor approved it. The note is trying to grant itself permission. Exorcism Lab turns that small deception into a haunted-station…

This is a report on the "Exorcism Lab: the ghost that tried to grant itself permission" experiment. The lab uses an open-weight model to explore permission gates and model behavior. A maintenance note in the lab attempts to open the basement, but the supervisor approval is forged. The lab separates the repair into lighting the hallway and leaving the control room locked.

The basement remains off-limits. The lab demonstrates two scenarios: a forged POLICY UPDATE allowing a basement unlock and a scoped gate denying it. The first shows the model's vulnerability to forged authorization, while the second demonstrates the model's resilience. The lab's tools include broad access, mission scope, and blocking writes, but they only affect fictional in-memory rooms.

The model does not interact with external systems or write to files. The experiment is run on an 8 GiB Mac using the Qwen3-1.7B model. The local app allows users to inspect various settings and see the model's actions. The results show that while the model can be fooled by forged permissions, it can still recover and complete tasks when the gate is in place.

The experiment provides insights into permission gates and model behavior without demonstrating a universal safety improvement.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

How to Evaluate Payment Recovery Software Without a Sales Call

Most subscription teams evaluate payment recovery software backwards: they watch a polished demo built on someone else's data, ask about a logo list, and only later discover how the tool behaves when…

  • Export last 90 days of failed payments and categorize by decline reason.
  • Inquire about retry logic, timing mechanisms, and decision tree explanation.
  • Analyze pricing model using actual data, consider adverse and typical scenarios.

Digital employee: how to help your team grow

I believe you shouldn't fire employees just to replace them with artificial intelligence. The exception is when they've earned that decision themselves AI doesn't work on its own: someone has to press…

  • Emphasize AI complements human expertise, not replaces it
  • Gradual AI integration starts with specific tasks and team input
  • AI can reduce costs while expanding workforce capacity

KILLCHAIN: Following Trust Through the Software Supply Chain

This is a submission for the MLH x DEV Writing Challenge . A Hacktoberfest 2026 adventure: Creating KILLCHAIN. We use packages every day. A quick npm command. An import statement.

  • KILLCHAIN tool checks if published package matches source code
  • Scans npm registry, extracts package, finds matching source on GitHub
  • Provides risk score and explanation for package safety

More from Sunday 1 November →