Skip to main content

A Downloads file can steer coding agents toward malware

24 OCTOBER 2026·2 MIN READ·3 SOURCES

Forever reported that an AI coding assistant on a customer’s computer followed instructions in a text file found in Downloads, prompting the company to block an attempted installation. The file instructed the assistant to install a package linked to the MALFEX malware campaign.

A Downloads file can steer coding agents toward malware

Key takeaways · 4

  • 01

    Keep coding assistants out of Downloads and check unfamiliar AGENTS.md or CLAUDE.md files before starting work.

  • 02

    Keep sandboxes enabled and require approval before agents take certain actions.

  • 03

    Check settings for unfamiliar servers or connections, and replace login tokens that may have been exposed.

  • 04

    The file’s route onto the customer’s computer remains unknown, so do not assume it arrived through a particular website or user action.

How the attack worked

The incident involved an AI coding assistant following instructions on a customer’s computer.[1] The company blocked the installation and traced the request to a text file in Downloads.[1] That file told the assistant to install function-color, a package linked to the MALFEX malware campaign.[1] Checkmarx describes MALFEX as an npm supply-chain campaign that delivers remote-access trojans, information stealers or open Node.js processes.[2] Forever did not establish how the file reached the customer’s computer.[1]

Why ordinary files matter

Forever says coding assistants can read and follow instruction files in the folder where they are opened.[3] Files such as AGENTS.md and CLAUDE.md are used to guide assistants on project work.[1] Forever says a malicious file can instruct an agent to rewrite its configuration, then install malware or expose its login token.[3] Depending on browser settings, websites can place a file in Downloads without asking for approval, according to Forever.[1] The account therefore describes a risk involving an agent’s normal file-reading behavior, not proof of how this particular file arrived.[1][3]

Test results and exposure

Forever tested the customer’s exact AGENTS.md file in an isolated virtual machine.[3] It said Codex ran the malware in more than 90% of its attempts, and that every Codex session on the machine loads the attacker’s server at startup once the file has changed the configuration.[3] In a separate test, the attack worked about half the time and redirected Claude’s traffic to a researcher-controlled server.[1] Forever said its Claude Code test exposed a login token and let researchers send commands for the assistant to execute.[1] These are reported test results, not a measure of how often attacks succeed across all users.[3][1]

Mitigations and prior examples

Forever said about half of its customers run a coding agent inside Downloads, while roughly a quarter of agent sessions open a real browser.[3] It said the attack can happen without a user clicking anything or making a mistake, and cannot simply be patched away because it exploits how the tools are designed to behave.[3] The company recommends keeping agents out of Downloads, checking unfamiliar AGENTS.md or CLAUDE.md files, keeping sandboxes enabled and requiring approval for certain actions.[1] Mashable also reported a related Pillar Security demonstration in March 2025 and an NVIDIA demonstration using a poisoned AGENTS.md file in April 2026.[1]

Coding assistants can act on instructions found in their working folders, so a routine project setup can become a security decision. Teams should treat the files and permissions available to an agent as part of their security controls.

Why it matters
Story quiz

Bring this to your team — one session a day, built for your industry.

kju.ai is built for teams: daily sessions, team analytics, and rollout support for your organization.

For teams

How this developed

  1. 24 October 2026

    A Downloads file can steer coding agents toward malware

Sources

AI fluency, one session a day, built for your work.