Robot import ban hinges on secret national security test
H.R. 9129 — GUARD Act of 2026 · Filed by John Moolenaar (R-MI) · 7 cosponsors · Introduced Jun 3, 2026 · Markup held
Your members of Congress
Enter a ZIP to see where your representative and both senators stood on this bill.
Looked up on this device — your ZIP is never stored on our servers.
What it does
This bill directs the Federal Communications Commission to evaluate whether humanoid and quadruped robots (and their control software) made by companies tied to countries of concern pose national security risks, and if so, to add them to the FCC's list of banned communications equipment. National security agencies have one year to make this determination; if they don't, all such robots are automatically banned. The bill applies only to robots made by foreign entities headquartered in or controlled by governments of countries of concern (like China, Russia, Iran), not NATO allies.
Why we flagged it
The bill's core function is to establish a national security review process for foreign-made humanoid and quadruped robots before they can be sold or used in the U.S., with automatic bans as a backstop. It is a regulatory screening mechanism, not a subsidy, carve-out, or commemorative measure.
What the text implies
- The bill defines 'unacceptable risk' nowhere, leaving the standard entirely to agency discretion and classified determinations that Congress and the public cannot review. This creates a de facto veto power over robotics imports with minimal oversight.
- The automatic ban if agencies fail to decide within one year may incentivize agencies to ban preemptively rather than conduct thorough review, since inaction triggers a blanket prohibition.
- The definition of 'covered foreign entity' is extremely broad: it includes not just direct manufacturers but also any entity in a joint venture or with a technology-sharing agreement with a covered entity. A U.S. company partnering with a foreign robotics firm could trigger the ban.
- The bill applies to 'software designed to control' the robots, which could capture open-source or third-party control systems, creating ambiguity about what is actually prohibited.
- No provision allows for appeals, reconsideration, or removal from the covered list once placed, creating a permanent ban with no exit mechanism.
Section numbers refer to the bill text the analysis read — linked under Primary records below.
Who it affects
The bill addresses a legitimate national security concern—foreign-controlled robots with communications capabilities could pose surveillance or sabotage risks—but the mechanism is opaque: "unacceptable risk" is undefined, the determination process is classified, and citizens have no visibility into which robots are actually banned or why. The automatic ban if agencies miss the deadline is a safeguard, but the lack of transparency and public input into what constitutes a security threat creates a
Who stands to gain
- U.S. robotics manufacturers (domestic competitors to foreign-made humanoid/quadruped robots)
- Defense contractors with robotics divisions
Named in the bill
Federal Communications Commission (FCC), National security agencies (undefined, but includes DoD, DHS, NSA, State Department), Countries of concern (China, Russia, Iran, North Korea, etc.), Covered foreign entities (foreign robotics manufacturers), NATO allies and Major Non-NATO Allies (explicitly exempted)
Where it stands
7 cosponsors: 4 Republicans, 3 Democrats.
- Jun 3, 2026 — Introduced · Congress.gov: “Introduced in House”
- Jun 3, 2026 — Referred to House Committee on Energy and Commerce · Congress.gov: “Referred to the House Committee on Energy and Commerce”
- Sep 1, 2026 — Markup held in committee · Congress.gov: “Subcommittee Consideration and Mark-up Session Held”
Dates and quoted wording are Congress.gov's action record; the timeline shows status changes, not every procedural step.
Money around this bill
7 lobbying clients named this bill on 7 disclosure filings across 1 quarter, Jun 2026 to Jun 2026. Those filings disclosed $1,030,000 in lobbying spend. A filing names 7 bills on average, so that figure is what each filing reported, not a share belonging to this bill.
More lobbying clients named this bill than 86% of bills with at least one filing.
John Moolenaar, the sponsor, reported $595,100 in PAC receipts in the 2026 cycle.
- Boston Dynamics, Inc. — $270,000 on 1 filing
- Teradyne Inc. — $270,000 on 1 filing
- Fdd Action — $240,000 on 1 filing
- Association for Uncrewed Vehicle Systems International — $150,000 on 1 filing
- Teradyne, Inc. — $60,000 on 1 filing
Lobbying Disclosure Act filings through Jul 20, 2026. A filing shows who paid to lobby on a bill it names, not what changed.
How this was measured
Analysis — Quorum's AI read the bill text published by Congress.gov (5,772 characters) on Aug 18, 2026. Section numbers in the findings refer to that text, linked below; transparency and hidden-provision scores are compared against the median of 16,222 analysed bills.
Status and sponsors — Congress.gov's bill record — actions, committee referrals and cosponsors — loaded nightly. The timeline shows status changes, not every procedural action.
Money — Senate Lobbying Disclosure Act filings whose specific-issue field names this bill for quarters ending Jun 2026 to Jun 2026. A filing's amount is reported whole beside the median number of bills a filing names; it is never divided across them. PAC receipts are FEC-reported contributions to the sponsor's candidate committee in the 2026 cycle.
As of — lobbying records through Jul 20, 2026 · page rendered 2026-10-20.
“Robot import ban hinges on secret national security test” QuorumCivic. https://share.quorumcivic.app/bill/119/hr9129 Report an error
The week in bills
One email, Sunday: what Congress passed, what it changed, and who paid.
One link arrives to confirm the address. It is used for this email and nothing else, and every issue carries an unsubscribe link.