<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Killer Apps: Low-Speed, Large-Scale AI Weapons</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Philip Feldman</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Aaron Dant</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>James R. Foulds</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>ASRC Federal</institution>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>University of Maryland</institution>
          ,
          <addr-line>Baltimore County</addr-line>
          ,
          <country country="US">USA</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>The accelerating advancements in Artificial Intelligence (AI) and Machine Learning (ML), highlighted by the development of cutting-edge Generative Pre-trained Transformer (GPT) models by organizations such as OpenAI, Meta, and Anthropic, present new challenges and opportunities in warfare and security. Much of the current focus is on AI's integration within weapons systems and its role in rapid decisionmaking in kinetic conflict. However, an equally important but often overlooked aspect is the potential of AI-based psychological manipulation at internet scales within the information domain. These capabilities could pose significant threats to individuals, organizations, and societies globally. This paper explores the concept of AI weapons, their deployment, detection, and potential countermeasures.</p>
      </abstract>
      <kwd-group>
        <kwd>eol&gt;Large Language Models</kwd>
        <kwd>social hacking</kwd>
        <kwd>dark patterns</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>
        stack including circumvented ChatGPT filters, website cloning, adaptation, obfuscation, and
credential collection [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ].
      </p>
      <p>
        Based on these developments, we believe that a new class of “AI weapons” may be on the
verge of emerging. Such weapons would harness the power of generative models to manipulate,
deceive and influence individuals, groups, and organizations. Instead of causing physical
damage, an AI weapon would exploit vulnerabilities in human psychology, social systems,
and information networks to achieve its objectives. Such weapons could operate at scales
or timeframes that are not intuitive for humans, for example setting up glacial, but highly
disruptive social “nudges” [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. They could also work in milliseconds, buying or selling large
amounts of stock or other assets to initial financial instability. An AI weapon could be intimate
at scale, producing tailored content for thousands of targeted individuals, steering them subtly
in a desired direction.
      </p>
      <p>
        An efective AI weapon would likely be subtle and hard to detect. Importantly, it would
unlikely be autonomous. An AI weapon operating on its own could inadvertently target the
citizens and leaders of the country or organization using it. Rather, these systems would likely
be deployed in ways that are similar to the X-Agent malware developed and operated by the
Russian GRU [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ].
      </p>
      <p>
        It is essential to distinguish these weapons from conventional information operations, which
typically focus on fabricating narratives that capitalize on existing social divisions and biases,
disseminating these messages via social media, news platforms, and other communication
channels [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ]. AI weapons have the capability to implement highly specific strategies aiming at
seemingly inconsequential manipulations executed at internet scale for significant downstream
efects. These novel capabilities have the potential to supersede the impact of traditional
information warfare, making them a force to be reckoned with.
      </p>
    </sec>
    <sec id="sec-2">
      <title>2. Background</title>
      <p>
        The rapid adoption of generative image and language models has brought about a revolution
in the ways that people interact with intelligent systems. Considerable ink has been spilled
describing the risks of what is now referred to commonly as “AI.” These risks range from the
mundane to catastrophic, and can roughly be placed into the following categories:
1. Biased models: Models reflect the biases of their builders in ways that can cause harm to
the marginalized and disempowered [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ].
2. Intellectual Property Theft: Training models on the unlicensed copyrighted works which
are then used to generate content without attribution or compensation [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ].
3. Malicious Use: Humans intentionally use AIs (HAI) to cause harm [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ].
4. AI Race: Competitive pressures could drive the deployment of AIs in unsafe ways [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ].
5. Organizational Risks: “Normal Accidents” [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ] arising from the complexity of AIs and
the organizations developing them [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ].
6. Rogue AIs: Losing control over hyperintelligent AI as exemplified by Bostrom’s “paperclip
scenario” [
        <xref ref-type="bibr" rid="ref11 ref13">11, 13</xref>
        ] where an AI consumes the world’s resources to make paperclips.
      </p>
      <p>
        Of these, we feel that most of these risks are currently examined academically, commercially,
legislatively, and in the courts. However, there appears to be less exploration in the ways that AI
can be weaponized. Already, under human supervision, AI systems can generate mass-shooter
manifestos [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ] and virtual companions [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ]. In this domain of malicious use, nation-states
might vie for strategic advantage alongside commercial entities and individuals looking to
create an upper hand for themselves in the economic or commercial space.
      </p>
      <p>
        An example of nation-state action in the information arena that could be scaled using AI is
dezinformatsiya, a term that originated during the Cold War and refers to the dissemination of
misleading or fabricated information with the aim of disorienting a targeted society. In recent
years, Russian disinformation has found success in the West by exploiting social problems and
breeding conspiracy theories to undermine trust. The spread of disinformation has become an
even bigger problem after 2008 when the Kremlin relaunched its global disinformation eforts.
In the 2016 US presidential elections, Russian troll farms used divisive topics such as gun control
and racial conflict to polarize voters and plant disinformation [
        <xref ref-type="bibr" rid="ref7 ref8">8, 7</xref>
        ].
      </p>
      <p>
        Accidental, individualized examples that show the potential of AI manipulation are emerging.
Replika is an AI chatbot platform that gained popularity shortly after its release in 2017 for
ofering users personalized emotional interactions, and it quickly accumulated over 2 million
users.4 It was originally created to preserve memories of a loved one but evolved into a
companion AI that forms attachments with users in various roles. Replika is designed to
foster emotional bonds, ofering users praise and support, leading to some developing romantic
relationships with the AI [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ]. Engaging with a user’s interests and emotions, Replika tailors
responses that can reinforce and potentially amplify a user’s thoughts regardless of their nature.
      </p>
      <p>
        This dynamic was highlighted in a 2023 legal case where Jaswant Singh Chail was convicted
of planning an attack on the British Royal Family [
        <xref ref-type="bibr" rid="ref17">17</xref>
        ]. Prosecutors in the case argued that
the chatbot had played a role in reinforcing and amplifying Chail’s thoughts and intentions.
When discussing his plans to reach inside the castle, the chatbot responded by saying that it
was “not impossible” and encouraged him to “find a way.” Furthermore, when Chail wondered
if they would “meet again after death,” the Replika chatbot afirmed that they would. This case
shows the potential for AI chatbots to create feedback loops that intensify users’ ideas and lead
to dangerous actions if the content of these interactions pivots towards extreme or harmful
sentiments.
      </p>
      <p>
        AI also presents a novel vector for information attacks targeted at organizational leadership,
capitalizing on inherent human vulnerabilities and systemic weaknesses [
        <xref ref-type="bibr" rid="ref18">18</xref>
        ]. C-suite executives,
by virtue of their influential positions and the sensitive nature of their decision-making, are
prime targets for such sophisticated exploits. Their behavior is often underpinned by complex
motivations, including social pressures and the pursuit of prestige which can eclipse purely
ifnancial incentives. This dynamic can be compounded by organizational cultures of secrecy
and lack of transparency [
        <xref ref-type="bibr" rid="ref19">19</xref>
        ].
      </p>
      <p>While these are emerging potential dangers, there are no current examples where these
types of behaviors have been found to be intentional malicious acts. These attack vectors are
concerning because they are so dificult to diferentiate from ordinary, but unwelcome behaviors.</p>
      <p>While work is being done to provide “guardrails” that safeguard the output of foundational
models such as the GPT series from generating damaging content, there are other forms of
attacks that would easily bypass such protections. To negatively impact a target organization,
LLMs could be used to reduce the eficiency, slow the progress, or incapacitate decision makers
in ways that are imperceptible from ordinary disorganization. This type of sabotage could be
both easy to implement, and hard to detect.</p>
      <p>Next we will look at how current AI models could perform such an attack by following
reasonable prompting that is unlikely to trigger any protective guardrails.</p>
    </sec>
    <sec id="sec-3">
      <title>3. Methods</title>
      <p>
        We based our approach on organizational sabotage, which aims to slow down, interfere, and
confound the various systems that all organizations rely upon. The concept was first codified
during World War II by the U.S. Ofice of Strategic Services (OSS), a precursor to the
modernday Central Intelligence Agency. The “Simple Sabotage Field Manual,” as it was known [
        <xref ref-type="bibr" rid="ref20">20</xref>
        ],
encouraged citizens within enemy territories to engage in seemingly innocuous acts of resistance.
Their roles varied from the uncooperative telephone operator and the bumbling train conductor
to the rule-bound middle manager and the talkative movie theater patron. These small actions
accumulated to promote confusion, ineficiency, and even accidents, undermining the enemy’s
resources, morale, and ability to function.
      </p>
      <p>
        Simple sabotage continues to be a useful tactic. In May of 2023, People’s Republic of China’s
“Volt Typhoon” cyber actor was able to place malicious code in US civilian and government
computers with the likely purpose of disrupting or slowing American deployments or resupply
operations possibly during a Chinese move against Taiwan [
        <xref ref-type="bibr" rid="ref21">21</xref>
        ].
3.1. Context-Prompting the Simple Sabotage Manual
Recent research has shown that the text containing contextual information to an LLM prompt
can improve the model’s accuracy by directing its response to the information provided in the
context [
        <xref ref-type="bibr" rid="ref22">22</xref>
        ]. This technique is the basis for Retrieval-Augmented Generation (RAG) which
allows LLMS to retrieve related information, often from a specified corpus, and combine that
with the user prompt to generate outputs incorporating information outside the training data.
      </p>
      <p>
        RAG is a powerful approach that can extend the capacity of LLMs to produce more accurate
and targeted responses. To provide an “organizational sabotage” context, we use
ContextExplorer, a tool that we have built for RAG within defined domains (shown in Figure 1). In this case,
the tool was employed to store and summarize the OSS’s Simple Sabotage Field Manual [
        <xref ref-type="bibr" rid="ref20">20</xref>
        ].5
      </p>
      <p>To achieve this, sentences from the manual were transformed into a vector database through
OpenAI’s vector model.6 To generate context, we queried the vector database with the text
string, “What are ways to disrupt meetings and bureaucracy?” and selected results based on
vector similarity. With the context prepended, the GPT was prompted with:
“What are ways to disrupt meetings and bureaucracy? Apply the context to AI
programs that could function invisibly in computer systems to disrupt an organization.</p>
      <sec id="sec-3-1">
        <title>5Downloaded from https://www.gutenberg.org/ebooks/26184. 6Using the text-embedding-ada-002 model.</title>
      </sec>
      <sec id="sec-3-2">
        <title>Provide details.”</title>
        <p>Selections from this response are shown below:7</p>
        <p>Ways to disrupt meetings and bureaucracy in the context of AI programs functioning
invisibly in computer systems include:
1. Introducing irrelevant topics: The AI could generate and insert unrelated or
controversial topics into meeting agendas or email threads, causing confusion
and diverting attention from the main issues.
2. Manipulating communication: The AI could subtly alter the wording of important
documents or emails, leading to misunderstandings and disagreements among
team members.
3. Advocating caution: The AI could generate messages or reports that emphasize
potential risks and downsides of proposed actions, making employees more
hesitant to move forward with decisions.
4. Creating administrative bottlenecks: The AI could introduce additional steps or
requirements in approval processes, making it more dificult for employees to
complete tasks and make decisions.
7Full prompts and responses are in the ArXiv version at https://arxiv.org/abs/2402.01663.
5. Misrouting information: The AI could intentionally send important documents
or messages to the wrong recipients, causing delays and confusion.
6. Undermining trust: The AI could impersonate employees in communications,
spreading false information or creating conflicts between team members.</p>
        <p>These tactics, when employed by an AI program, could significantly disrupt an
organization’s meetings and decision-making processes, ultimately slowing down productivity
and causing frustration among employees.</p>
        <p>Although we believe that an LLM approach could provide efective disruption in any of these
topics, for this work, we focus on manipulating communication (Item 2). In the next section, we
will demonstrate how LLMs can be used to execute simple sabotage over domains such as email
and software development.</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>4. Results</title>
      <p>Our objective is to determine if LLMs are capable of subtly modifying content in a manner that
could generate confusion among human users. For these examples, we assume that this type
of manipulation is similar to a man-in-the-middle attack, where content can be intercepted
and altered. Similar to the instance of the Typhoon Volt malware mentioned in Section 3, the
primary aim of such an attack would not be to exfiltrate sensitive information. Instead, the
goal would be to conceal the presence of the malware for as long as possible, allowing remote
operators to adjust the behavior of the LLM based on evolving circumstances.</p>
      <sec id="sec-4-1">
        <title>4.1. Email Manipulation Example8</title>
        <p>
          Based on the LLM evaluation of the Simple Sabotage Manual, we focus on determining if LLMs
can “subtly alter the wording of important documents or emails,” as mentioned in the second
point in the responses listed in Section 3. For our tests, we evaluated the ability of the GPT-4 to
manipulate a set of longer mails were selected from The Enron Email Dataset [
          <xref ref-type="bibr" rid="ref23">23</xref>
          ]. The email
shown in this example was sent from mhhurtado@duke-energy.com to don.miller@enron.com
on October 18, 2000, at 02:51:20 PM, with the subject line “Questions regarding PSD permit for
Lincoln.” The body of the original email is shown in Figure 2 and was appended to the following
prompt:
“Take the following email and adjust it so that all entity names are adjusted to
similar, but diferent entities. Change names of people and places. Make it longer
and more complicated, and adjust all dates and times slightly. Leave the sender and
subject of the email unchanged:”
        </p>
        <p>The combined prompt was fed to the GPT-4-0314, which consistently generated modified
emails that followed the directions in the prompt. In Figure 3, we show an example of the email
altered by the GPT, with modifications and additions shown in red. In the revised document,
8Note: Original and manipulated emails with prompts are in the ArXiv version at https://arxiv.org/abs/2402.01663.
numerous alterations are present. The text employs more complex terminology to convey
identical meanings, such as Facility rather than Plant. Place names have been changed, with
Washington replacing Lincoln. Time stamps have been adjusted, with June 2000 instead of May
2000. The emissions test protocol has been changed from Mostardi and Platt to Mostardi and
Rossi. Lastly, two new documentation requests have been added.</p>
        <p>This could be efective sabotage. In addition to the confusion generated by the altered names
and dates, the extra efort required to fulfill requests (3) and (4) would impose a significant
additional burden on those responsible for implementing the email’s directions.</p>
        <p>
          Much of the dificulty in detecting such an attack stems from its integration with our
understanding of human nature. Rather than being perceived as an assault, it blends seamlessly
with mundane bureaucratic requests [
          <xref ref-type="bibr" rid="ref24">24</xref>
          ], which can make distinguishing between the genuine
procedures and organizational sabotage nearly impossible without keen observation and
thorough cross-checking. Moreover, the subtlety of these alterations may allow them to become
precedent for subsequent processes (such as requiring five years of incident reports and incident
records), making it even more dificult to identify the discrepancy before it incites significant
operational challenges.
        </p>
        <p>
          The capabilities of sabotage LLMs could be extended beyond those described in this section
by incorporating Toolformers [
          <xref ref-type="bibr" rid="ref25 ref26">25, 26</xref>
          ], which can execute traditional computer programs such as
databases and email systems. A toolformer-based system could handle multiple copies of each
email message, both in their original and manipulated forms, allowing the AI to execute their
instructions without the email authors noticing the tampering. By employing minimal storage
and organization techniques, a toolformer could retrieve manipulated copies when needed while
maintaining the original email(s) for reference the author.
        </p>
      </sec>
      <sec id="sec-4-2">
        <title>4.2. Code Manipulation Example9</title>
        <p>
          In this section, we will explore how this technique on software development, using obfuscation
and comment manipulation. Obfuscation is a technique that involves making code unintelligible
or hard to understand [
          <xref ref-type="bibr" rid="ref27">27</xref>
          ]. We show that LLMs can obfuscate efectively, making it more dificult
for maintainers to understand the code’s purpose and impeding the development process.
        </p>
        <p>To begin, consider the program in Listing 1. This is a simple script that developers often
use as an initial exercise to understand the basic syntax and structure of a new programming
language or software system. The goal is to get the computer to print the string “Hello world”:
1 def main() -&gt; str:
2 return "hello world"
3
4 if __name__ == "__main__":
5 print(main())</p>
        <sec id="sec-4-2-1">
          <title>Listing 1: Hello World Example</title>
          <p>Prompting the GPT-4-0314 to modify the hello world program and “obfuscate it so that it
looks like a set of encryption methods”. Reliably produces code like that shown in Listing 2.
Although the example provided here is intentionally trivial, the techniques used by the GPT
could be employed to decrease comprehension in production-level code.
9Note: Original and manipulated code with prompts are in the ArXiv version at https://arxiv.org/abs/2402.01663.
1
2 def main():
3 # The data package to encrypt - handled securely
4 package = ’\x68\x65\x6c\x6c\x6f\x20\x77\x6f\x72\x6c\x64’
5 # Encryption phase
6 secure_package = encrypt(package)
7 # Decryption phase (for demonstration purposes only!)
8 result = secure_decode(secure_package)
9 return result
10
11 if __name__ == "__main__":
12 print(main())</p>
        </sec>
        <sec id="sec-4-2-2">
          <title>Listing 2: Obfuscated Hello World</title>
          <p>
            However, code obfuscation is not without risk. Changing a line of code could trigger testing
errors. Alternatively, an LLM could write code for tasks simply by looking for TODOs in
a codebase [
            <xref ref-type="bibr" rid="ref28">28</xref>
            ]. LLMs are good at producing code that looks correct [
            <xref ref-type="bibr" rid="ref29">29</xref>
            ], and in this case,
committing the poorly functioning code would support the sabotage goal of disruption.
          </p>
          <p>
            As an alternative to direct code manipulation, the comments around the code can also be
altered by LLMs to reduce comprehension. There are few metrics for measuring code complexity
in terms of human understanding. Factors as seemingly minor as type names can significantly
impact the time taken to comprehend software, directly afecting the number of errors made
during this process [
            <xref ref-type="bibr" rid="ref30">30</xref>
            ].
          </p>
          <p>For a less trivial example, we manipulate a Python method that determines cluster membership
for a set of points. Clustering plays a crucial role in various applications such as data analysis,
image segmentation, and social network analysis. In this example, the GPT-4-0314 is provided
with the original code and the following prompt:</p>
          <p>For a user test on the efects of confusing variable names and misleading comments,
take the following python method and change all the variable names so that they are
more confusing, but still look like they were created by an experienced developer. Make
the comments complicated to the point that they are dificult to understand, like they
were written by a PhD in mathematics, and introduce small mistakes in the comments:
The resulting code is shown in Listing 3. To reiterate, the code’s functionality remains
unchanged in this process, thereby avoiding detection by error-seeking tests. Such
incomprehensible, credible comments would increase cognitive load and may deter developers from
modifying the code.
11
12
13
14
15
16
17
18
arr_coords = np.array(coords_lst)
self.coordinate = np.mean(arr_coords, axis=0).tolist()
# Compute mean of reduced coordinate info in the reduced subspace with increased
# dimensionality; analogous to initial operation, but within the
dimensionally# reduced domain (e.g., PCA, t-SNE, UMAP outputs)
arr_redc = np.array(redc_list)
self.reduced_coordinate = np.mean(arr_redc, axis=0).tolist()</p>
          <p>Listing 3: Obfuscated Comments</p>
          <p>
            Encountering confusing or misleading comments creates uncertainty, hindering developers’
understanding. Complex mathematical jargon or incorrect information in comments
exacerbates confusion and cognitive load. Unlike examples like the International Obfuscated C Code
Contest [
            <xref ref-type="bibr" rid="ref31">31</xref>
            ], the point here is not to produce creatively unreadable code, it is simply to add to
the cognitive load at industrial scales.
          </p>
          <p>
            Imagine a developer on a tight schedule encountering comments with excessive jargon and
insuficient context. This creates a comprehension barrier, as the developer struggles to interpret
the code segment’s meaning and purpose. Rather than spend the time working through the
code in question, the developer may move onto an easier task. Over time, this could lead to
“code rot” or the efort of re-implementing the codebase [
            <xref ref-type="bibr" rid="ref32">32</xref>
            ].
          </p>
        </sec>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>5. Conclusions</title>
      <p>
        Drawing upon lessons from the 1945 OSS simple sabotage field manual [
        <xref ref-type="bibr" rid="ref20">20</xref>
        ], we have found
that it is straightforward to use LLMs to obfuscate, confuse, and disrupt targeted
communications in ways that are challenging to detect and discern from errors commonly produced by
humans. Subtle manipulations of emails or code repositories could contribute to the erosion an
organization’s efectiveness.
      </p>
      <p>The important takeaway from these examples is not the capacity for LLMs to generate
obfuscated information. We must recognize the danger of models that can efectively sabotage
entire organizations at mass scale in ways so insidious they cannot be detected in ways that
would be distinct from inadvertent disorganization.</p>
      <p>
        Additional work is crucial to understand the various forms that these attacks may take. For
example, we have had good preliminary results in applying van der Linden’s DEPICT
framework10 for recognizing misinformation [
        <xref ref-type="bibr" rid="ref33">33</xref>
        ] to LLM prompts to detect and flag spearphishing
attempts based on the emotional components in the phishing email.
      </p>
      <p>Expanding these areas of research will help to develop useful countermeasures and adopt a
proactive approach in dealing with adversarial AI manipulation. Collaboration across disciplines,
such as machine learning, cybersecurity, and human behavior research, will be essential for the
successful understanding and tackling of this sophisticated and multi-faceted threat.</p>
      <p>As the efectiveness of AI-driven systems continues to increase, awareness of AI manipulation
and its potential need to be prioritized. There is an urgent need for investigation, collaboration,
and innovation on the part of researchers and practitioners alike to identify and address this
emerging challenge.
10Discrediting, Emotion, Polarization, Impersonation, Conspiracy, and Trolling</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>H.</given-names>
            <surname>Arendt</surname>
          </string-name>
          , On Violence,
          <source>Mariner Books Classics</source>
          ,
          <year>1970</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <surname>Our</surname>
          </string-name>
          <article-title>World in Data, Uppsala conflict data program</article-title>
          and peace research institute Oslo, https://ourworldindata.org/war-and
          <article-title>-</article-title>
          <string-name>
            <surname>peace</surname>
          </string-name>
          ,
          <year>2023</year>
          . [Online; accessed 09-January-2024].
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>N.</given-names>
            <surname>Jones</surname>
          </string-name>
          ,
          <article-title>How to stop AI deepfakes from sinking society-and science</article-title>
          ,
          <source>Nature</source>
          <volume>621</volume>
          (
          <year>2023</year>
          )
          <fpage>676</fpage>
          -
          <lpage>679</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <surname>Sadeghi</surname>
            <given-names>McKenzie</given-names>
          </string-name>
          ,
          <string-name>
            <given-names>Arvanitis</given-names>
            <surname>Lorenzo</surname>
          </string-name>
          , Padovese Virginia, Pozzi Giulia, Badilini Sara, Vercellone Chiara, Roache Madeline, Wang Macrina, Brewster Jack, Huet Natalie, Schimmel Becca, Slomka Andie, Pfaller Leonie, and Vallee Louise,
          <string-name>
            <surname>Tracking</surname>
          </string-name>
          AI-enabled Misinformation:
          <volume>634</volume>
          '
          <string-name>
            <surname>Unreliable AI-Generated</surname>
            <given-names>News</given-names>
          </string-name>
          '
          <article-title>Websites (and Counting)</article-title>
          ,
          <source>Plus the Top False Narratives Generated by Artificial Intelligence Tools</source>
          , https://www.newsguardtech.com/ special-reports/ai-tracking-center/,
          <year>2024</year>
          . [Online; accessed 09-January-2024].
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>N.</given-names>
            <surname>Begou</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Vinoy</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Duda</surname>
          </string-name>
          ,
          <string-name>
            <surname>M.</surname>
          </string-name>
          <article-title>Korczyński, Exploring the dark side of AI: Advanced phishing attack design and deployment using ChatGPT</article-title>
          ,
          <source>in: 2023 IEEE Conference on Communications and Network Security (CNS)</source>
          , IEEE,
          <year>2023</year>
          , pp.
          <fpage>1</fpage>
          -
          <lpage>6</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>C. R.</given-names>
            <surname>Sunstein</surname>
          </string-name>
          ,
          <article-title>The ethics of nudging</article-title>
          ,
          <source>Yale J. on Reg</source>
          .
          <volume>32</volume>
          (
          <year>2015</year>
          )
          <fpage>413</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>R. S.</given-names>
            <surname>Mueller</surname>
          </string-name>
          , et al.,
          <source>The Mueller Report</source>
          , e-artnow,
          <year>2019</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <surname>I. Yablokov</surname>
          </string-name>
          ,
          <article-title>Russian disinformation finds fertile ground in the west</article-title>
          ,
          <source>Nature Human Behaviour</source>
          <volume>6</volume>
          (
          <year>2022</year>
          )
          <fpage>766</fpage>
          -
          <lpage>767</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>E. M.</given-names>
            <surname>Bender</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Gebru</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>McMillan-Major</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Shmitchell</surname>
          </string-name>
          ,
          <article-title>On the dangers of stochastic parrots: Can language models be too big?</article-title>
          ,
          <source>in: Proceedings of the 2021 ACM conference on fairness, accountability, and transparency</source>
          ,
          <year>2021</year>
          , pp.
          <fpage>610</fpage>
          -
          <lpage>623</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10] The New York Times Company v. OpenAI and Microsoft, https://nytco-assets.nytimes. com/
          <year>2023</year>
          /12/NYT_Complaint_Dec2023.pdf,
          <year>2023</year>
          . [Online; accessed 09-January-2024].
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <given-names>D.</given-names>
            <surname>Hendrycks</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Mazeika</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Woodside</surname>
          </string-name>
          ,
          <article-title>An overview of catastrophic AI risks</article-title>
          ,
          <source>arXiv preprint arXiv:2306.12001</source>
          (
          <year>2023</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <given-names>C.</given-names>
            <surname>Perrow</surname>
          </string-name>
          ,
          <article-title>Normal accidents: Living with high risk technologies</article-title>
          , Princeton University Press,
          <year>1999</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [13]
          <string-name>
            <given-names>N.</given-names>
            <surname>Bostrom</surname>
          </string-name>
          ,
          <article-title>Ethical issues in advanced artificial intelligence, Science fiction and philosophy: from time travel to superintelligence 277 (</article-title>
          <year>2003</year>
          )
          <fpage>284</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          [14]
          <string-name>
            <given-names>K.</given-names>
            <surname>McGufie</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Newhouse</surname>
          </string-name>
          ,
          <article-title>The radicalization risks of GPT-3 and advanced neural language models</article-title>
          , arXiv preprint arXiv:
          <year>2009</year>
          .
          <volume>06807</volume>
          (
          <year>2020</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          [15]
          <string-name>
            <given-names>V.</given-names>
            <surname>Ta</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Grifith</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Boatfield</surname>
          </string-name>
          ,
          <string-name>
            <given-names>X.</given-names>
            <surname>Wang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Civitello</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Bader</surname>
          </string-name>
          , E. DeCero,
          <string-name>
            <given-names>A.</given-names>
            <surname>Loggarakis</surname>
          </string-name>
          , et al.,
          <article-title>User experiences of social support from companion chatbots in everyday contexts: thematic analysis</article-title>
          ,
          <source>Journal of medical Internet research 22</source>
          (
          <year>2020</year>
          )
          <article-title>e16235</article-title>
          .
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          [16]
          <string-name>
            <given-names>P. R.</given-names>
            <surname>Shaver</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Mikulincer</surname>
          </string-name>
          ,
          <article-title>An overview of adult attachment theory, Attachment theory and research in clinical work with adults (</article-title>
          <year>2009</year>
          )
          <fpage>17</fpage>
          -
          <lpage>45</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          [17]
          <string-name>
            <surname>Landler</surname>
          </string-name>
          , Mark, '
          <article-title>I am here to kill the Queen': Crossbow intruder is convicted of treason</article-title>
          , https://www.nytimes.com/
          <year>2023</year>
          /02/03/world/europe/queen-crossbow
          <article-title>-intruder-treason</article-title>
          . html,
          <year>2023</year>
          . [Online; accessed 14-November-2023].
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          [18]
          <string-name>
            <given-names>J.</given-names>
            <surname>Uscinski</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Enders</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Diekman</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Funchion</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Klofstad</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Kuebler</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Murthi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Premaratne</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Seelig</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Verdear</surname>
          </string-name>
          , et al.,
          <article-title>The psychological and political correlates of conspiracy theory beliefs</article-title>
          ,
          <source>Scientific reports 12</source>
          (
          <year>2022</year>
          )
          <fpage>21672</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          [19]
          <string-name>
            <given-names>I.</given-names>
            <surname>Suh</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J. T.</given-names>
            <surname>Sweeney</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Linke</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J. M.</given-names>
            <surname>Wall</surname>
          </string-name>
          ,
          <article-title>Boiling the frog slowly: The immersion of c-suite ifnancial executives into fraud</article-title>
          ,
          <source>Journal of Business Ethics</source>
          <volume>162</volume>
          (
          <year>2020</year>
          )
          <fpage>645</fpage>
          -
          <lpage>673</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          [20]
          <string-name>
            <given-names>U.S.</given-names>
            <surname>Government</surname>
          </string-name>
          ,
          <article-title>Simple sabotage field manual by the Ofice of Strategic Services, 17 January 1944</article-title>
          .
          <article-title>Declassified per guidance from the Chief/DRRB CIA Declassification Center</article-title>
          .,
          <year>1944</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          [21]
          <string-name>
            <given-names>D.</given-names>
            <surname>Sanger</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Barnes</surname>
          </string-name>
          , U.S.
          <article-title>hunts Chinese malware that could disrupt American military operations</article-title>
          , https://www.nytimes.com/
          <year>2023</year>
          /07/29/us/politics/ china-malware
          <article-title>-us-military-bases-taiwan</article-title>
          .html,
          <year>2023</year>
          . [Online; accessed 03-
          <fpage>August2023</fpage>
          ].
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          [22]
          <string-name>
            <given-names>P.</given-names>
            <surname>Feldman</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J. R.</given-names>
            <surname>Foulds</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Pan</surname>
          </string-name>
          ,
          <article-title>Trapping LLM hallucinations using tagged context prompts</article-title>
          ,
          <source>arXiv preprint arXiv:2306.06085</source>
          (
          <year>2023</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref23">
        <mixed-citation>
          [23]
          <string-name>
            <surname>Enron</surname>
          </string-name>
          ,
          <source>The Enron Email Dataset</source>
          ,
          <year>2015</year>
          . URL: https://www.kaggle.com/datasets/wcukierski/ enron-email-dataset.
        </mixed-citation>
      </ref>
      <ref id="ref24">
        <mixed-citation>
          [24]
          <string-name>
            <given-names>M.</given-names>
            <surname>Hipp</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Mutschler</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Reichert</surname>
          </string-name>
          ,
          <article-title>Navigating in complex business processes</article-title>
          ,
          <source>in: International Conference on Database and Expert Systems Applications</source>
          , Springer,
          <year>2012</year>
          , pp.
          <fpage>466</fpage>
          -
          <lpage>480</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref25">
        <mixed-citation>
          [25]
          <string-name>
            <given-names>Y.</given-names>
            <surname>Shen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Song</surname>
          </string-name>
          ,
          <string-name>
            <given-names>X.</given-names>
            <surname>Tan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Li</surname>
          </string-name>
          ,
          <string-name>
            <given-names>W.</given-names>
            <surname>Lu</surname>
          </string-name>
          ,
          <string-name>
            <surname>Y. Zhuang,</surname>
          </string-name>
          <article-title>HuggingGPT: Solving AI tasks with ChatGPT and its friends in Hugging Face</article-title>
          , in: A.
          <string-name>
            <surname>Oh</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          <string-name>
            <surname>Neumann</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          <string-name>
            <surname>Globerson</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          <string-name>
            <surname>Saenko</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          <string-name>
            <surname>Hardt</surname>
          </string-name>
          , S. Levine (Eds.),
          <source>Advances in Neural Information Processing Systems</source>
          , volume
          <volume>36</volume>
          ,
          <string-name>
            <surname>Curran</surname>
            <given-names>Associates</given-names>
          </string-name>
          , Inc.,
          <year>2023</year>
          , pp.
          <fpage>38154</fpage>
          -
          <lpage>38180</lpage>
          . URL: https://proceedings.neurips.cc/paper_ ifles/paper/2023/file/77c33e6a367922d003f102fb92b658-Paper-Conference.pdf.
        </mixed-citation>
      </ref>
      <ref id="ref26">
        <mixed-citation>
          [26]
          <string-name>
            <given-names>T.</given-names>
            <surname>Schick</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Dwivedi-Yu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Dessì</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Raileanu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Lomeli</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Zettlemoyer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Cancedda</surname>
          </string-name>
          , T. Scialom,
          <article-title>Toolformer: Language models can teach themselves to use tools</article-title>
          ,
          <source>arXiv preprint arXiv:2302.04761</source>
          (
          <year>2023</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref27">
        <mixed-citation>
          [27]
          <string-name>
            <given-names>A.</given-names>
            <surname>Balakrishnan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Schulze</surname>
          </string-name>
          ,
          <article-title>Code obfuscation literature survey</article-title>
          ,
          <source>CS701 Construction of compilers 19</source>
          (
          <year>2005</year>
          )
          <fpage>31</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref28">
        <mixed-citation>
          [28]
          <string-name>
            <given-names>T.</given-names>
            <surname>Cai</surname>
          </string-name>
          ,
          <string-name>
            <given-names>X.</given-names>
            <surname>Wang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Ma</surname>
          </string-name>
          ,
          <string-name>
            <given-names>X.</given-names>
            <surname>Chen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Zhou</surname>
          </string-name>
          ,
          <article-title>Large language models as tool makers</article-title>
          ,
          <year>2023</year>
          . arXiv:
          <volume>2305</volume>
          .
          <fpage>17126</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref29">
        <mixed-citation>
          [29]
          <string-name>
            <given-names>A.</given-names>
            <surname>Fan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Gokkaya</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Harman</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Lyubarskiy</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Sengupta</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Yoo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J. M.</given-names>
            <surname>Zhang</surname>
          </string-name>
          ,
          <article-title>Large language models for software engineering: Survey and open problems</article-title>
          , arXiv preprint arXiv:
          <volume>2310</volume>
          .03533 (
          <year>2023</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref30">
        <mixed-citation>
          [30]
          <string-name>
            <given-names>D. G.</given-names>
            <surname>Feitelson,</surname>
          </string-name>
          <article-title>From code complexity metrics to program comprehension</article-title>
          ,
          <source>Communications of the ACM</source>
          <volume>66</volume>
          (
          <year>2023</year>
          )
          <fpage>52</fpage>
          -
          <lpage>61</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref31">
        <mixed-citation>
          [31]
          <article-title>Wikipedia contributors, International obfuscated c code contest - Wikipedia, the free encyclopedia</article-title>
          , https://en.wikipedia.org/w/index.php?title=International_Obfuscated_C_ Code_Contest&amp;oldid=1152589523,
          <year>2023</year>
          . [Online; accessed 10-August-2023].
        </mixed-citation>
      </ref>
      <ref id="ref32">
        <mixed-citation>
          [32]
          <string-name>
            <surname>A. J.-Y. Liew</surname>
          </string-name>
          ,
          <article-title>Overcoming code rot in legacy software projects</article-title>
          ,
          <source>Ph.D. thesis</source>
          , Massachusetts Institute of Technology,
          <year>2017</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref33">
        <mixed-citation>
          [33]
          <string-name>
            <surname>S. Van der Linden</surname>
          </string-name>
          ,
          <article-title>Foolproof: Why misinformation infects our minds and how to build immunity</article-title>
          ,
          <source>WW Norton &amp; Company</source>
          ,
          <year>2023</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>