{
	"id": "1b848edc-050c-4948-8ac1-a31ce5f55a41",
	"created_at": "2026-04-06T00:17:46.274763Z",
	"updated_at": "2026-04-10T13:11:54.718652Z",
	"deleted_at": null,
	"sha1_hash": "46874c3631029f5df52181ae9b21bd85ca3e2ccb",
	"title": "Merlin for Red Teams",
	"llm_title": "",
	"authors": "",
	"file_creation_date": "0001-01-01T00:00:00Z",
	"file_modification_date": "0001-01-01T00:00:00Z",
	"file_size": 393895,
	"plain_text": "Merlin for Red Teams\r\nBy Action Dan\r\nArchived: 2026-04-02 12:44:57 UTC\r\nWelcome back Internet people! Lately I've seen a rise in AI generated articles, blog posts, and even book content. I\r\nneed to say loudly, as a reader, this is a major turnoff. If a reader can tell that something was written by AI, then\r\nthe tools are being used poorly. Please don’t pass off LLM output directly as human writing. It makes your\r\nwork output feel cheap. AI should be used as a writing tool, it shouldn't be replacing human writers altogether. \r\nWhen writers use LLM output verbatim the result is often stale and lacks clarity. In many cases, it actually makes\r\nideas harder to understand. Current LLMs struggle to maintain consistent, logical models of complex ideas. So\r\nwhile the writing may sound polished at first, it sometimes misrepresents concepts or drifts into conflicting,\r\nmultiple definitions. Moving past the coherency issues, it's often obvious when a writer has an overreliance on\r\nverbatim LLM output. There are many obvious tells. From the overuse of the em dash, to the nonsensical use of\r\nthe colon; AI generated content sticks out to those who use frontier models often. Certain phrasing patterns also\r\nstand out. For example: “It’s not X, it’s Y.” As a writer, this often feels like filler. Just write about Y. Just because\r\nthese are the current form of these tells doesn't mean these are universal or ubiquitous tells. Quite the opposite,\r\nthese will change over time as the models change, but the heavy users of the models will very likely recognize\r\ntheir output when used verbatim. \r\nDon't get me wrong, I'm not saying don't use LLMs to help you write. I previously wrote about how to use AI in\r\nyour technical writing, such as creating templates, voice files, and dynamic prompts to generate rich content. It\r\nalso makes for a great editor! But one of the key takeaways there is in the last paragraph, where I emphasize\r\nheavily modifying and adapting the output. You can't use the output verbatim; frontier LLM output is just too\r\nrecognizable. \r\nI recently read this great and thoughtful article titled \"Don't Let AI Write For You\", where Alex Woods lays out\r\nthat the point of writing is to develop and cement thoughts worth communicating, not simply generating words or\r\ncontent. I couldn't agree with this more. I often use LLMs to help expand on ideas, or think about edge cases I\r\nmight be considering. I use it to help me refine my writing prompts and generate starting points. But very rarely\r\ndo I use the ideas or output verbatim. It's an incredibly useful tool, but in my opinion it shouldn't replace the art all\r\ntogether. \r\nSo I'll repeat it, and I hope somewhere out there other writers take it to heart. When writers use LLM output\r\nverbatim it comes across as incredibly lazy. And frankly, why would anyone read that? A reader could just prompt\r\nthe model themselves and get the same result.\r\nhttp://lockboxx.blogspot.com/2018/02/merlin-for-red-teams.html\r\nPage 1 of 2\n\nSource: http://lockboxx.blogspot.com/2018/02/merlin-for-red-teams.html\r\nhttp://lockboxx.blogspot.com/2018/02/merlin-for-red-teams.html\r\nPage 2 of 2",
	"extraction_quality": 1,
	"language": "EN",
	"sources": [
		"Malpedia"
	],
	"origins": [
		"web"
	],
	"references": [
		"http://lockboxx.blogspot.com/2018/02/merlin-for-red-teams.html"
	],
	"report_names": [
		"merlin-for-red-teams.html"
	],
	"threat_actors": [],
	"ts_created_at": 1775434666,
	"ts_updated_at": 1775826714,
	"ts_creation_date": 0,
	"ts_modification_date": 0,
	"files": {
		"pdf": "https://archive.orkl.eu/46874c3631029f5df52181ae9b21bd85ca3e2ccb.pdf",
		"text": "https://archive.orkl.eu/46874c3631029f5df52181ae9b21bd85ca3e2ccb.txt",
		"img": "https://archive.orkl.eu/46874c3631029f5df52181ae9b21bd85ca3e2ccb.jpg"
	}
}