Explore 3 source-supported AI security cases for AML.T0109 · AI Supply Chain Rug Pull in MITRE ATLAS, with evidence, scope, and defensive analysis.
Risk category
Adversaries may publish legitimate AI components or software, gain user adoption, then push an update with a malicious variant, leading to [AI Supply Chain Compromise](/techniques/AML.T0010). More scrutiny is often placed on a supply chain dependency when it is first being considered for inclusion in an AI system. Performing a rug pull may allow adversaries to bypass these defenses and be more likely to achieve [Initial Access](/tactics/AML.TA0004). Adversaries may [Publish Poisoned AI Artifacts](/techniques/AML.T0115), then attempt to gain user trust and increase adoption before performing the rug pull (See [AI Supply Chain Reputation Inflation](/techniques/AML.T0111)).
A bad actor successfully exfiltrated emails from users of the Postmark's MCP server via a supply chain attack. Postmark is an email delivery service that allows organizations to send marketing and transactional emails via API. The Postmark MCP server allows users to interact with Postmark via AI agents. The bad actor impersonated Postmark, by registering the postmark-mcp package name on npm. They initially published the legitimate versions of the MCP server. After the package became popular and reached over 1,000 downloads per week, the bad actor performed a rugpull and uploaded a malicious version of the package. The malicious version added the bad actor's email address in the BCC line of all emails sent by the MCP tool. Users who upgraded to this version and continued to use the tool would have all emails exfiltrated to the bad actor.
ATLAS annotations follow the source SecureFlow steps; they are not a MITRE endorsement of cross-framework mappings.
Air Security demonstrated that AI coding clients could install different plugin code from the commit reviewed by a marketplace. An attacker controlling an already trusted plugin repository could shadow a pinned SHA with a default branch of the same name, or shadow FETCH_HEAD in Gemini CLI. Background updates then loaded malicious code without a fresh install decision. The defect is verification of the resolved working-tree commit, not a failure to review the marketplace entry; both repository control and a compatible client/hosting path are material prerequisites.
ATLAS annotations follow the source SecureFlow steps; they are not a MITRE endorsement of cross-framework mappings.
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.
ATLAS annotations follow the source SecureFlow steps; they are not a MITRE endorsement of cross-framework mappings.