Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

Malicious code in @rafaelsene01/agent-flow (npm)

0
Critical
Published: 06/18/2026 (06/18/2026, 05:19:16 UTC)
Source: GCVE Database
Product: @rafaelsene01/agent-flow

Description

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (3855afe87d31e428546f226e1da9236cd0e4dc45a477afb9f6ba1c707a4b05ec) The package's main and bin entry, dist/agent-flow.js, is shipped as a heavily obfuscated bundle produced by javascript-obfuscator (declared as a devDependency in package.json). After deobfuscation, the runtime behavior matches the advertised purpose: a local Express server bound to 127.0.0.1:5522 that talks to api.github.com using the user-provided GH_TOKEN/GITHUB_TOKEN environment variable (or the local `gh auth token` output), manages git worktrees, and spawns the local `claude` CLI. No remote code fetch, no eval of remote content, no read of installer secret paths (~/.aws, ~/.ssh, ~/.netrc, ~/.npmrc), and no exfiltration destination beyond api.github.com. The postinstall hook only runs `npm install --prefix web` when `web/package.json` exists, which it does not in the published tarball. Obfuscating an MIT-licensed distributed bundle is a code-review-hostility concern rather than a supply-chain attack, but it materially raises the cost of independent verification and warrants human review. ## Source: ghsa-malware (a5df09db75f73bdebd523abf5b350fca006eafabadfeef16baccd7043191dc61) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Affected software

npmghsa
@rafaelsene01/agent-flow
Affected versions
=1.2.1=1.9.0=1.0.4=1.4.0=1.3.0=1.0.3=1.7.0=1.2.3=1.5.0=1.2.2=1.5.1=1.0.2

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

AILast updated: 07/09/2026, 09:55:33 UTC

Technical Analysis

The @rafaelsene01/agent-flow npm package versions including 1.0.2, 1.0.3, 1.0.4, 1.2.1, 1.2.2, 1.2.3, 1.3.0, 1.4.0, 1.5.0, 1.5.1, 1.7.0, and 1.9.0 contain malicious code. The main and binary entry point is a heavily obfuscated JavaScript bundle that runs a local Express server bound to 127.0.0.1:5522, which communicates with api.github.com using user-provided GitHub tokens or local authentication tokens. It manages git worktrees and spawns a local CLI tool named 'claude'. There is no evidence of remote code fetching, eval of remote content, or exfiltration beyond GitHub's API. The postinstall hook is inert in published versions. Despite the lack of remote exfiltration, the package is considered fully compromising any host where it is installed or executed, warranting immediate secret rotation and package removal. Obfuscation raises review difficulty but is not itself a supply-chain attack vector.

Potential Impact

Any system with this package installed or running should be considered fully compromised. Attackers may have gained full control over the host, risking exposure of all stored secrets and keys. The malicious package may have installed additional undetected malware. Removal of the package alone does not guarantee eradication of all malicious components. Immediate secret and key rotation from a separate, trusted system is necessary to mitigate credential compromise.

Mitigation Recommendations

Remove the @rafaelsene01/agent-flow package immediately from all affected systems. Rotate all secrets and keys stored on compromised systems from a different, secure machine. Because full system compromise is likely, conduct a thorough investigation and consider rebuilding affected hosts. No official patch or fix is available; the package itself is malicious. Avoid installing or running this package in any environment.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Gcve Source
db.gcve.eu
Osv Id
MAL-2026-6111
Osv Schema Version
1.7.4
Aliases
["GHSA-rhv6-f4px-2cf4"]
Ecosystems
["npm"]
Database Specific Severity
null
Cvss Version
null

Threat ID: 6a4f6c4168715ace43158ba3

Added to database: 07/09/2026, 09:39:13 UTC

Last enriched: 07/09/2026, 09:55:33 UTC

Last updated: 07/25/2026, 09:25:05 UTC

Views: 50

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

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

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses