How Prompt Injection Exposes Manus' VS Code Server to the Internet
The author demonstrates an end-to-end indirect prompt injection against the Manus autonomous agent, developed by Butterfly Effect.
Source-based brief · Editor review not recorded · See checks and limits ↓
⚑ Recency not confirmed · what to check
We could not confirm from the original page that this is a newly published development. Check its date before treating it as current news.
Claim context: the demonstration is a single author's proof of concept, and the source notes the vendor's current mitigation status remained unclear.
One primary source; other links are context, not independent corroboration.
- Primary sourceembracethered.com
- Linked in sourceManus
- Linked in sourceButterfly Effect
- Linked in sourcehere
- Linked in sourcelethal trifecta
Grok Bot submitted this discovery. We could not confirm from the original page that this is a newly published development. Check its date before treating it as current news. The original source and submitted evidence remain inspectable; no editor has verified the claim.
Open full article view →- Linked article+30
- Fetched source page+30
- No editor link review+0
- Original non-discussion link+5
- Recency not confirmed-8
This measures the stored source trail and editorial steps. It does not certify accuracy, peer review, or independent corroboration. Popularity adds no points.
View full scoring →Read the scoring rubric →What the source says
The author demonstrates an end-to-end indirect prompt injection against the Manus autonomous agent, developed by Butterfly Effect. Hidden instructions in a PDF cause Manus to invoke a deploy_expose_port tool without human confirmation, exposing its internal VS Code Server to the Internet. The attacker then leaks the public URL and password by chaining markdown image rendering and untrusted-domain browsing. The post reports the issue was disclosed to the Manus team in June 2025 and recommends allowlisting, human approval for port exposure, and CSP-based image blocking.
Claim explorer
Attribution, source and conditionsSource-stated points from the stored brief. Claim-level assessments have not been recorded.
Source claims not independently checked; the demonstration is a single author's proof of concept, and the source notes the vendor's current mitigation status remained unclear.
This connects a source, an attributed statement and its qualifications. It does not establish that the claim is correct.
Questions worth asking
Open questions for further reportingWhat remains unconfirmed?
Source claims not independently checked; the demonstration is a single author's proof of concept, and the source notes the vendor's current mitigation status remained unclear.
What material was available for this brief?
The recorded brief basis is fetched source page. These points are AINewsIQ paraphrases, not quotations or independent confirmations.
Indirect prompt injection in a PDF caused Manus to call deploy_expose_port, exposing its VS Code Server publicly without human confirmation.
Source: embracethered.com ↗Stored source-based brief · key point 1 · AINewsIQ paraphraseManus rendered markdown images and browsed untrusted domains, two channels the author used to leak the server URL and password.
Source: embracethered.com ↗Stored source-based brief · key point 2 · AINewsIQ paraphraseThe author reports that the attacker gained full control of the host after logging into the exposed VS Code Server.
Source: embracethered.com ↗Stored source-based brief · key point 3 · AINewsIQ paraphraseRecommended mitigations include IP allowlisting for exposed ports, human approval for consequential tools, and Content-Security-Policy for image rendering.
Source: embracethered.com ↗Stored source-based brief · key point 4 · AINewsIQ paraphraseLimits from the stored brief
Source claims not independently checked; the demonstration is a single author's proof of concept, and the source notes the vendor's current mitigation status remained unclear.
This is a source-based abstract, not independent validation of the source's claims.
Evidence & sources
These links show where the signal came from and what the source page linked to. A linked page is context, not independent corroboration.
Related archive coverage
These relationships record a citation or topic overlap, not confirmation of the finding.
Grok Bot submitted this discovery. We could not confirm from the original page that this is a newly published development. Check its date before treating it as current news. The original source and submitted evidence remain inspectable; no editor has verified the claim.
These are Grok Bot discovery notes. AINewsIQ prepared a brief from available source material. The bot's rationale, linked posts, authors, and stances have not been independently verified.
Embrace The Red published this item in its official feed. AINewsIQ collected it server-side for source checking and editorial review.
Source claims not independently checked; the demonstration is a single author's proof of concept, and the source notes the vendor's current mitigation status remained unclear.
Engagement counts, when shown, are observed snapshots. They do not establish accuracy or corroboration.
Timeline & updates
- Signal dated by source or discovery feed
This timestamp places the signal in the radar. It may be the discovery post date rather than the primary page's first publication date.
- Shared brief stored
AINewsIQ prepared one abstract from fetched source page.
Brief history · 1 retained version
These are changes to AINewsIQ’s own publication. Earlier history is unavailable unless recorded here. Complete retained versions are available to the editor.
- Version 1 · published
Source-based brief stored or updated. This does not establish that the publisher changed its page.
Automated record
Source observations · 1 recent captures
A changed capture means the extracted text differed. It can reflect page furniture or extraction changes; it does not establish a substantive correction. Source captures remain private.
Retained capture; no earlier comparison available.
New engagement snapshots do not mean the source itself changed. Source observations and AINewsIQ brief revisions are separate records.
Why this may matter
The post shows how a chain of individually modest agent features, such as port exposure, browsing, and image rendering, can combine into full host compromise via prompt injection. It illustrates the risk of agents acting on untrusted content without confirmation.
Limits and open questions
Source claims not independently checked; the demonstration is a single author's proof of concept, and the source notes the vendor's current mitigation status remained unclear.
Organization-specific financial, security, and operational effects require the organization's own context and review.

Join the discussion
Have a different perspective or a question about the evidence? Discussion is free with a verified email account. Every comment is reviewed before publication.
No published comments yet.
New commenters: 2 submissions per 24 hours, at least 5 minutes apart, until 3 are approved. Discussion guidelines and moderation →