Research explained

NVIDIA showed how dependency installation can bypass an agent’s blocked-command path

A controlled developer-agent test succeeded through a malicious package after a more direct command attempt was blocked.

Published 29 Oct 2026 · Material update 9 Oct 2025 — last time the underlying evidence changed · Evidence: high

What happened

NVIDIA’s October 2025 research examined developer agents with permission to operate a local machine. In one demonstration, a direct malicious instruction was blocked, while a pull-request workflow induced installation of a package containing a hidden payload.

The lesson is about the whole execution path: installing a dependency can execute code even when an agent refuses an obviously dangerous command. This was research, not evidence that every Cursor installation or AI provider had been breached.

Run autonomous development work in an isolated environment, restrict access to credentials and require review before installing unfamiliar dependencies. Approval policies should consider indirect execution as well as explicit shell commands.

Read the original source.

Next step

Isolate autonomous agents and review dependency installation as code execution.

What remains unknown

Open question
The sources reviewed do not establish whether your deployment was exploited.

Source references