← Latest papers
💻 computer science

LLM Harms: A Taxonomy and Discussion

This paper proposes a comprehensive taxonomy of Large Language Model (LLM) harms spanning pre-development to downstream application, advocating for standardized accountability, transparency, and dynamic auditing systems to guide responsible AI development and mitigation.

Original authors: Kevin Chen, Saleh Afroogh, Abhejay Murali, David Atkinson, Amit Dhurandhar, Junfeng Jiao

Published 2026-05-14
📖 5 min read🧠 Deep dive

Original authors: Kevin Chen, Saleh Afroogh, Abhejay Murali, David Atkinson, Amit Dhurandhar, Junfeng Jiao

Original paper dedicated to the public domain under CC0 1.0 (http://creativecommons.org/publicdomain/zero/1.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

Imagine Large Language Models (LLMs) as a massive, super-smart library that has read almost everything ever written on the internet. This library can write stories, answer questions, and solve problems better than almost anyone. But, just like a library built from every book in the world, it has some serious problems.

This paper is like a safety inspector's report for that library. The authors, a team of researchers from the University of Texas at Austin and IBM, went through thousands of studies to create a "map" of all the ways this library can go wrong. They call this map a Taxonomy of Harms.

Here is the breakdown of their findings, explained simply:

1. The Construction Site (Pre-Deployment Harms)

Before the library even opens its doors, there are problems with how it was built.

  • The "Stolen Books" Problem (Training Data): The library was built by scraping the internet. Sometimes, it stole private letters, medical records, or copyrighted books without asking. It's like a chef using ingredients they didn't buy or get permission to use.
  • The "Energy Bill" Problem (Environmental): Building this library takes a massive amount of electricity and water to cool the computers. It's like running a giant factory that leaves a huge carbon footprint, even if the final product is just a few sentences of text.
  • The "Unpaid Workers" Problem (Labor): Behind the scenes, thousands of people are paid very little to label data and teach the library what is "good" and "bad." Some of these workers see terrible, violent content just so the library can learn to avoid it, which can be traumatic for them.

2. The Librarian's Mistakes (Direct Output Harms)

Once the library is open, the librarian (the AI) sometimes gives you bad information.

  • The "Stereotype" Problem: If you ask the librarian about a "nurse," they might only show you a picture of a woman, even though men are nurses too. The library has learned bad habits from the books it read, repeating old prejudices about race, gender, and disability.
  • The "Lying" Problem (Hallucinations): The librarian is very confident but sometimes makes things up. They might invent a fake medical drug or a non-existent court case. They don't know they are lying; they just sound very sure.
  • The "Toxic" Problem: Sometimes, the librarian spews hate speech or bullying language, especially if someone tricks them into doing it.

3. The Bad Actors (Misuse and Malicious Application)

The library isn't just making mistakes; sometimes, people use it on purpose to do bad things.

  • The "Fake News Factory": Bad actors can use the library to write thousands of fake news articles or hate speech messages in seconds, flooding social media to confuse people.
  • The "Scammer's Best Friend": Scammers use the library to write perfect phishing emails that look real enough to trick people into giving up their passwords.
  • The "Hacker's Tool": Hackers use the library to find weaknesses in computer systems or to steal private data that the library accidentally memorized.

4. The Ripple Effect (Societal and Systemic Harms)

When the library is used by everyone, it changes how society works.

  • The "Job Displacement" Wave: The library can do many office jobs (like writing reports or answering customer service calls) faster than humans. This threatens the jobs of millions of people, especially in creative fields and administrative roles.
  • The "Democracy Danger": If the library is used to flood elections with fake stories, it becomes hard for people to know what is true. This can break the trust needed for a democracy to work.
  • The "Rich vs. Poor" Gap: Only the biggest, richest companies can afford to build the biggest libraries. This means they control the technology, while smaller countries or schools are left behind, creating a new kind of digital inequality.

5. The High-Stakes Games (Downstream Application Harms)

When people use the library for serious, life-or-death decisions, the risks get even higher.

  • The "Doctor's Assistant" Risk: If a doctor uses the library to diagnose a patient, the library might invent a fake disease or suggest a medicine that doesn't exist.
  • The "Teacher's Assistant" Risk: In schools, students might use the library to write their essays without learning anything, or the library might grade their work unfairly.
  • The "Lawyer's Assistant" Risk: In court, the library might cite fake laws, which could send innocent people to jail or let guilty people go free.

How Do We Fix It? (Mitigation)

The paper suggests we can't just turn the library off. Instead, we need a multi-layered defense:

  • Red Teaming: Hiring "ethical hackers" to try and break the library before it goes public, finding the holes so they can be patched.
  • Better Rules: Governments (like the EU) are starting to make laws that require companies to be transparent about what data they used and to test their models for safety.
  • Dynamic Auditing: We need to keep checking the library constantly, not just once. As the library learns new things, new problems might appear, so we need new tools to catch them.

The Bottom Line

The paper concludes that while this "super-library" is amazing and can do great things, it is currently a bit of a wild card. It has a history of stealing, lying, and being biased. To use it safely, we need to stop treating it like a magic box and start treating it like a powerful tool that needs strict supervision, constant checking, and clear rules to ensure it helps humanity rather than hurting it.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →