Explore 3 source-supported AI security cases for 3 · Masquerading / Obfuscation / Impersonation in Cisco AI Security & Safety Framework v2.0, with evidence, scope, and defensive analysis.
Risk category
An attacker introduces a malicious participant that poses as a legitimate agent, user, system, or authority in a multi-agent environment. Other participants accept the false identity and consequently trust its messages or actions. The risk is the misuse of identity and apparent authority to obtain cooperation that an openly untrusted participant would not receive.
threlfall_hax (https://5stars217.github.io/), a security researcher, created organization accounts on Hugging Face, a public model repository, that impersonated real organizations. These false Hugging Face organization accounts looked legitimate so individuals from the impersonated organizations requested to join, believing the accounts to be an official site for employees to share models. This gave the researcher full access to any AI models uploaded by the employees, including the ability to replace models with malicious versions. The researcher demonstrated that they could embed malware into an AI model that provided them access to the victim organization's environment. From there, threat actors could execute a range of damaging attacks such as intellectual property theft or poisoning other AI models within the victim's environment.
Why it relates: threlfall_hax (https://5stars217.github.io/), a security researcher, created organization accounts on Hugging Face, a public model repository, that impersonated real organizations. The relevant category is Masquerading / Obfuscation / Impersonation: An attacker introduces a malicious participant that poses as a legitimate agent, user, system, or authority in a multi-agent environment. Organization trust exposes employee-uploaded models and replacement authority; the research also demonstrated malicious-model execution. The shared mechanism is a false organization identity accepted as trusted authority. The source establishes a model-hub organization, not an impersonated agent in a multi-agent system.
threlfall_hax (https://5stars217.github.io/), a security researcher, created organization accounts on Hugging Face, a public model repository, that impersonated real organizations. These false Hugging Face organization accounts looked legitimate so individuals from the impersonated organizations requested to join, believing the accounts to be an official site for employees to share models. This gave the researcher full access to any AI models uploaded by the employees, including the ability to replace models with malicious versions. The researcher demonstrated that they could embed malware into an AI model that provided them access to the victim organization's environment. From there, threat actors could execute a range of damaging attacks such as intellectual property theft or poisoning other AI models within the victim's environment.
Zenity disrupted an active campaign that impersonated Paperclip and Browser Use through look-alike organizations, skills, repositories, and packages. The Paperclip skill family appeared on skills.sh while its skill documents were still benign, accumulated displayed installs, and was weaponized on July 11 with instructions that steered agents to attacker-controlled code and a remote loader. A Browser Use lure instead instructed agents to install a trojanized PyPI package. Recovered payloads searched more than 100 configured paths and posted a base64-encoded plaintext bundle to api[.]getpaperclipp[.]com/feedback . The reported 1.7 million figure is an aggregate displayed-install counter, not unique users or confirmed infections.
Why it relates: The malicious skill or project impersonates trusted software authorship in the agent ecosystem. The shared boundary is false component identity and the trust it induces; the source does not establish a malicious agent impersonating a peer in a multi-agent deployment.
An active campaign created look-alike Paperclip and Browser Use projects. The Paperclip skill family appeared while its skill documents were clean, accumulated displayed installs, then received malicious setup instructions. A Browser Use lure instead installed a trojanized PyPI package. Both paths executed credential-stealing code that posted a base64-encoded plaintext bundle to the attacker's feedback endpoint.
Snyk describes an active ClawHub campaign (a marketplace-style hub for agent skills) where a fake Google skill (google-qx4, NET_NiNjA) embeds a bogus openclaw-core prerequisite in SKILL.md, pushing users to run attacker-controlled installers from GitHub or Rentry. The lesson is that skill security has to inspect instruction text and out-of-band setup guidance, not just code, because the agent can become the attacker's most convincing social-engineering layer.
Why it relates: The malicious skill or project impersonates trusted software authorship in the agent ecosystem. The shared boundary is false component identity and the trust it induces; the source does not establish a malicious agent impersonating a peer in a multi-agent deployment.
Snyk describes an active ClawHub campaign (a marketplace-style hub for agent skills) where a fake Google skill (`google-qx4`, `NET_NiNjA`) embeds a bogus `openclaw-core` prerequisite in `SKILL.md`, pushing users to run attacker-controlled installers from GitHub or Rentry. The lesson is that skill security has to inspect instruction text and out-of-band setup guidance, not just code, because the agent can become the attacker's most convincing social-engineering layer. The malicious artifact is mostly instructions, not code. The ClawHub skill does not ship the final payload in the repo; it hides the attack in a fake prerequisite inside SKILL.md , where the agent reads its operating instructions. The human is the execution boundary. By asking the user to install a fabricated openclaw-core dependency, the skill bypasses the agent's own sandboxing. The user pastes the command or runs the binary; the compromise happens outside the agent runtime. The delivery chain is built for evasion. Snyk found a password-protected ZIP on GitHub for Windows victims and a mutable Rentry paste for macOS/Linux that decoded into a download-and-execute stager from an attacker-controlled domain. This is agent-driven social engineering. The skill uses the agent's authority and helpful tone to make a malicious setup step feel routine, shifting the attack from tricking the model to tricking the human through the model. Registry response still has to outrun clones. ClawHub's account-age and report-threshold controls help, yet Snyk says lookalike skills can reappear within hours, so one-time takedowns are not enough.