Log

Unethical Research: How to Create a Malevolent Artificial Intelligence

Sapience Technical Report STR 2016-03

Author: Roman V. Yampolskiy

Cybersecurity research involves publishing papers about malicious exploits as much as publishing information on how to design tools to protect cyber-infrastructure. It is this information exchange between ethical hackers and security experts, which results in a well-balanced cyber-ecosystem. In the blooming domain of AI Safety Engineering, hundreds of papers have been published on different proposals geared at the creation of a safe machine, yet nothing, to our knowledge, has been published on how to design a malevolent machine.

Availability of such information would be of great value particularly to computer scientists, mathematicians, and others who have an interest in AI safety, and who are attempting to avoid the spontaneous emergence or the deliberate creation of a dangerous AI, which can negatively affect human activities and in the worst case cause the complete obliteration of the human species. This paper provides some general guidelines for the creation of a Malevolent Artificial Intelligence (MAI).

Contents

  • Why the paper on this topic?
  • Hazardous Intelligent Software
  • Who might be interested in creating Malevolent AI?
  • How to create a Malevolent AI
  • Societal Impact

Cite as: Roman V. Yampolskiy. “Unethical Research: How to Create a Malevolent Artificial Intelligence“. arXiv:1605.02817 [cs.AI], Sapience Project, Technical Report STR 2016-3 (May 2016)

Full Report

Related posts:

Five More Lessons about Documentation: A follow-up to Mark Birch’s “Developer Documentation”

Last week’s DevBizOps blog entry (“Developer Documentation: Developers don’t like writing docs, what’s the alternative?“) asked: How programmers can get their answers from documentation, and are there alternatives? As ever Mark’s post advises on questions every developer has to ask in understanding software. Open source or proprietary, documentation is necessary either for using, extending, or changing software. The costs of searching for answers are known to developers and project managers. Empirical literature and decades of research in software comprehension and reverse engineering show that the costs of understanding software are significant. What, then, can be done? We offer five more lessons in addition to Mark’s post, presented as “formulas”:

Can AI be creative?

Last month Deep Mind’s latest AI broke another record, winning 5-0 against one of the world’s strongest professional players. This victory forces us to revisit our preconceptions and recognise how creative machine learning has become.

Leave a Reply