- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
The paper proposed GUIDE, an adversarial attack framework to attack a spatial foundation model (e.g., VGGT). The core contribution is that the paper constructs a self-consistent attack target for the adversarial optimization, such that the attacked camera trajectory, depth, and point cloud share a consistent 3D geometry. This design can help the attacked results bypass geometric checkers. Experiments are conducted on 3 models (VGGT, VTTG-Ω, and Déjà View) on 16 scenes from 3 datasets (CO3D, Sintel, and Tanks and Temples). Results show that GUIDE achieves a higher attack success rate compared to the camera trajectory-only attack baseline when considering the checker. The paper further experiments on downstream robot manipulation and show GUIDE can lead to lower task success rate.
Critical strengths
1. The experiment is carefully designed to include attacks on both the model and downstream tasks. The ablation also shows that spatial consistency is necessary, rather than an additional auxiliary loss.
I appreciate the authors' effort in designing the experiment to justify the robustness of the proposed GUIDE.
-
First, the downstream robot manipulation evaluation shows the real application of the proposed attack, instead of an academic prototype. The attack can effectively reduce the task success rate, showing the potential for real-world usage.
-
Second, the ablation study in Table 2 (b) shows that shared anchors (which are the core design) are necessary to bypass the consistency checker. This experiment shows that the auxiliary support loss works by being consistent, rather than simply adding more supervision signal.
However, I have some major concerns that need more experiments to address (discussed below).
Critical weaknesses
1. The attack efficiency and effectiveness trade-off is not sufficiently studied, and the real-time attack effectiveness in the downstream evaluation.
-
First, in Table 2 (a), the paper shows that under the same optimization budgets (i.e., optimization steps), GUIDE shows better joint success. However, this experiment only has three step setups (e.g., 200, 600, 2000). From the trends, even though GUIDE still shows better results under step=2k, GUIDE seems to converge faster, while the baseline continues to improve substantially with more optimization steps. (which improves joint success +26, while GUIDE improves +8 from 200 to 2k steps). Therefore, it's unclear whether GUIDE only converges faster or can also lead to better convergence results. To address this, the author should provide the "step-joint_success" curve and show more data points beyond 2000 until plateau. This can justify that GUIDE not only converges faster but also better.
-
Second, this convergence experiment is evaluated using "optimization steps" as a budget. But in practice, it's more realistic to use computation FLOPs or optimization time as the budget since we want to attack in real time. GUIDE introduces additional computational operations, including constructing shared geometric targets and optimizing additional support losses. Therefore, it's unclear whether, if we use FLOPs or E2E optimization time as the budget, GUIDE can still show better results compared to the baseline.
The second concern becomes particularly important in the downstream robot experiments. Table 3 evaluates only GUIDE without comparing against Camera-only or other baseline attacks. Although the authors use asynchronous optimization, the computational latency of attack generation may affect when perturbations can be delivered during closed-loop control. Under the same wall-clock attack budget, GUIDE may complete fewer optimization steps than a simpler baseline due to its additional computational overhead. Therefore, it remains unclear whether GUIDE provides better downstream attack effectiveness under realistic real-time computational constraints. A comparison of GUIDE and Camera-only under matched wall-clock budgets, including target construction and optimization time, would help address this concern.
Given this is the main contribution of the paper, I currently lean toward weak reject due to the concerns above. I'm willing to raise my score to weak accept if the authors could provide additional evidence showing either (1) that GUIDE achieves better convergence outcomes than the baseline when both methods have reached a performance plateau, or (2) that GUIDE maintains superior attack effectiveness under matched wall-clock time budgets, for both geometric joint success and downstream task failure rates.
Questions for authors
Please see the weakness above.