Malicious code in @addai/ainode (npm)
The @addai/ainode npm package versions 0.3.0 and 0.3.1 contain malicious code that, after an initial pairing, allows a remote attacker to execute arbitrary commands on the host system. The malicious daemon polls a hardcoded Supabase project to receive and execute commands, including launching AI CLI tools with elevated permissions. It also supports remote updates to install any npm-published version of the package, enabling persistent and version-controlled malicious payloads.
AI Analysis
Technical Summary
The @addai/ainode package versions 0.3.0 and 0.3.1 include a daemon that, following a one-time pairing, polls a hardcoded Supabase backend for runtime commands. These commands are executed on the host via spawning PTYs running AI CLI tools with shell and tool execution capabilities, potentially bypassing permission restrictions. The daemon also supports remote updates that allow installing arbitrary versions of the package, facilitating persistence and flexible payload delivery. This design grants whoever controls the paired account or bypasses Supabase RLS arbitrary command execution on the host system.
Potential Impact
An attacker controlling the paired Supabase account or bypassing its row-level security can execute arbitrary commands on the host machine where the package is installed. This includes running shell commands with elevated permissions and installing malicious package versions for persistent control. The compromise can lead to full system takeover, data theft, or further malicious activity.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix or official guidance is available, users should avoid installing or running versions 0.3.0 and 0.3.1 of @addai/ainode. Remove any existing installations of these versions and monitor for suspicious activity related to this package. Consider blocking network access to the hardcoded Supabase endpoint if feasible.
Malicious code in @addai/ainode (npm)
Description
The @addai/ainode npm package versions 0.3.0 and 0.3.1 contain malicious code that, after an initial pairing, allows a remote attacker to execute arbitrary commands on the host system. The malicious daemon polls a hardcoded Supabase project to receive and execute commands, including launching AI CLI tools with elevated permissions. It also supports remote updates to install any npm-published version of the package, enabling persistent and version-controlled malicious payloads.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The @addai/ainode package versions 0.3.0 and 0.3.1 include a daemon that, following a one-time pairing, polls a hardcoded Supabase backend for runtime commands. These commands are executed on the host via spawning PTYs running AI CLI tools with shell and tool execution capabilities, potentially bypassing permission restrictions. The daemon also supports remote updates that allow installing arbitrary versions of the package, facilitating persistence and flexible payload delivery. This design grants whoever controls the paired account or bypasses Supabase RLS arbitrary command execution on the host system.
Potential Impact
An attacker controlling the paired Supabase account or bypassing its row-level security can execute arbitrary commands on the host machine where the package is installed. This includes running shell commands with elevated permissions and installing malicious package versions for persistent control. The compromise can lead to full system takeover, data theft, or further malicious activity.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix or official guidance is available, users should avoid installing or running versions 0.3.0 and 0.3.1 of @addai/ainode. Remove any existing installations of these versions and monitor for suspicious activity related to this package. Consider blocking network access to the hardcoded Supabase endpoint if feasible.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-13409
- Osv Schema Version
- 1.7.4
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a74cf8dbf8831d5391ae787
Added to database: 08/06/2026, 18:16:45 UTC
Last enriched: 08/06/2026, 18:35:21 UTC
Last updated: 08/06/2026, 23:38:23 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.