Skip to content

Your installer file on your website is distributing malware #7736

Closed

Description

@melbazpeach-source

Description

The download link button then windows install - the exe installer has been infected with malware.

Plugins

No response

OpenCode version

No response

Steps to reproduce

No response

Screenshot and/or share link

No response

Operating System

No response

Terminal

No response

Activity

  1. github-actions commented on Jan 11, 2026

    @github-actions
    Contributor

    This issue might be a duplicate of existing issues. Please check:

    These issues describe similar Windows Defender/Security detections of malware (primarily Trojan:Script/Wacatac variants) related to OpenCode releases. It appears this is a known recurring issue that the team is actively working to address with code signing and other measures.

    Feel free to ignore if this describes a different specific case.

  2. melbazpeach-source commented on Jan 11, 2026

    @melbazpeach-source
    Author

    Maybe - but it’s NOT a signing issue - it’s self replicating and definitely a virus. Claude code scanned its files in the temp folder

  3. rekram1-node commented on Jan 11, 2026

    @rekram1-node
    Collaborator

    I think this is a false positive, what are you referring to that was causing issues in temp folder?

  4. melbazpeach-source commented on Jan 11, 2026

    @melbazpeach-source
    Author

    No it is not a false positive.
    I’ve double checked and it is absolutely malware.
    And these guys KNEW.
    It’s been flagged before and nothing was fixed.
    Now I’ve had to completely wipe my device and lost days of work.

  5. rekram1-node commented on Jan 11, 2026

    @rekram1-node
    Collaborator

    ? please share more?

  6. melbazpeach-source commented on Jan 11, 2026

    @melbazpeach-source
    Author

    CRITICAL: This is MALWARE
    File: C:\users\melba\AppData\Local\Temp.7cdd8f5e2b77f7b9-00000000.node
    Why it’s malware:
    1. Naming pattern matches known malware - .GUID-00000000.node is identical to Trojan pattern
    2. Created during infection - 1:53 PM today (same timeframe as malware detection)
    3. No digital signature - NotSigned
    4. Large size - 3.6 MB, unusual for a temp Node.js addon
    5. Hash identified - specific malware signature

  7. Mirrowel commented on Jan 11, 2026

    @Mirrowel

    This is a common windows defender L. This can trigger for archives with no binaries whatsoever.

    WIndows defender is nothing but trouble - disable it.

    Naturally, claude is clearly incorrect.
    You asked it and from your question an LLM will try to answer positively using whatever it can find. They are not trained to answer no and to disprove.

  8. Xavier-Burger commented on Jan 11, 2026

    @Xavier-Burger

    CRITICAL: This is MALWARE
    File: C:\users\melba\AppData\Local\Temp.7cdd8f5e2b77f7b9-00000000.node
    Why it’s malware:

    1. Naming pattern matches known malware - .GUID-00000000.node is identical to Trojan pattern
    2. Created during infection - 1:53 PM today (same timeframe as malware detection)
    3. No digital signature - NotSigned
    4. Large size - 3.6 MB, unusual for a temp Node.js addon
    5. Hash identified - specific malware signature

    Instead of relying on llm hallucinations, Google the old fasion way. There's a reason the detection is inconsistent on different open code versions, the temp dll and node files are being heuristically detected as Trojans. Look into the contributors behind opencode, these people aren't malicious or idiots.

  9. Makishima commented on Jan 11, 2026

    @Makishima
  10. melbazpeach-source commented on Jan 11, 2026

    @melbazpeach-source
    Author

    I have completely wiped my 2week old computer now.
    So as soon as your installer hit my system, it:
    Tried to install 10 copies of itself.
    It hammered my security.
    Security stopped 9.
    1 version got through.
    In the 10 seconds it took for me to take my system offline, it had already created 5 replicas of uts payload in my temp drive.
    It had altered group policy
    And it had changed the date on all the files it touched to tomorrow’s date.

    So honestly?
    I don’t know if that’s what your code is supposed to do but common sense says it’s not.
    If it is, I apologise.

    The fact you are all fobbing it off as false positive, and letting peoples machines get fkd over, is not doing much for the UX nor trustworthiness of your products tbh.

  11. Mirrowel commented on Jan 11, 2026

    @Mirrowel

    Upload to virustotal. What you are describing has nothing to do with what opencode does.
    By install you mean this? curl -fsSL https://opencode.ai/install | bash
    Windows installer:
    https://www.virustotal.com/gui/file/3fcb5f22adbfa3ef280d8aaae529148e56853e62b3bfdad16b321dc651475561

  12. Makishima commented on Jan 11, 2026

    @Makishima
  13. 4cecoder commented on Jan 13, 2026

    @4cecoder
    Image

    opentui.dll depenency is tripping up the windows 666 beast

    when cloning the source code windows quickly quarantines the node_modules/opentui/opentui.dll

    Image
  14. melbazpeach-source commented on Jan 13, 2026

    @melbazpeach-source
    Author
  15. Vagenda commented on Jan 14, 2026

    @Vagenda

    I'm old enough to remember when people cared about infections on their PC. Hell, I remember when people valued their privacy and rights as well. I read the report. It's a big enough red flag for me. Do better.

  16. thdxr commented on Jan 14, 2026

    @thdxr
    Member

    i just went through everything that was posted here

    nothing stands out to me - opencode has a binary dep called opentui which gets extracted on first run to a .dll and then called into with FFI

    seems like some scans look at this and feel like it's similar behavior to malware

    if someone can point to something more specific we're happy to take a look - i've checked our CI process and nothing has changed

    same binaries produced as always

    additionally everyone here is trying to help your issue - being insulting isn't particularly helpful

  17. thdxr commented on Jan 14, 2026

    @thdxr
    Member

    one thing that did stand out was this path

    "H:\baidu\netdisk\pc-international-unite\src\node_modules\uiohook-napi"

    this is what your security report is about - i don't know what this is and it's unrelated to opencode

    is this your project?

  18. melbazpeach-source commented on Jan 14, 2026

    @melbazpeach-source
    Author

    That stood out for me too.
    I’ve have no idea what “H:\baidu\netdisk\pc-international-unite\src\node_modules\uiohook-napi" is.
    It’s not my machine or projects.

    Look it’s done.
    No amount of complaint is going to give me back my machine.

    I’ve looked into anecdotal observations online, and I’d say either your link was (or is still) targeted for drive by malware.
    It’s cos your repo is popular and also why it’s random.
    Or maybe targeted in the npm malware attack.

    Just my 10 cents worth that it might be a good idea to increase your defenses.
    I’m no one. So my opinion doesn’t matter.
    But if it happens to someone who does matter, your software suffers by association.

  19. melbazpeach-source commented on Jan 16, 2026

    @melbazpeach-source
    Author

    I've done further analysis and that path:

    That path H:\baidu\netdisk\pc-international-unite\src\node_modules\uiohook-napi is literally the file path on the malware author’s development machine where they built/compiled the infected OpenCode package.

    When developers compile code, sometimes the build process embeds the full file paths from their development environment into the binary. The malware author forgot to strip this metadata out before releasing it.

    So this tells us:
    About the malware author:
    ∙ Uses Baidu Netdisk (Chinese cloud storage) on their H: drive
    ∙ Developing in the “pc-international-unite” project folder
    ∙ Using Node.js with uiohook-napi (keyboard/mouse hooking library)
    ∙ Either Chinese-speaking or deliberately using Chinese infrastructure
    What this means:
    ∙ This is NOT Hybrid Analysis’s path - it’s evidence baked into the malware itself
    ∙ It’s an OPSEC failure by the attacker (they leaked their dev environment)
    ∙ The uiohook-napi library explains autonomous mouse movement

    • the attacker’s own development path accidentally embedded in the code.
  20. 1076585426 commented on Jan 20, 2026

    @1076585426

    我进行了进一步分析,发现这条路径是:

    路径 H:\baidu\netdisk\pc-international-unite\src\node_modules\uiohook-napi 实际上是恶意软件作者在其开发机器上构建/编译受感染 OpenCode 包的文件路径。

    开发者编译代码时,有时构建过程会将开发环境中的完整文件路径嵌入到二进制文件中。恶意软件作者在发布前忘记移除这些元数据。

    因此,这告诉我们: 关于恶意软件作者: ∙ 使用百度网盘(中国云存储)托管在其 H 盘 ∙ 在“pc-international-unite”项目文件夹中进行开发 ∙ 使用 Node.js 和 uiohook-napi(键盘/鼠标钩子库) ∙ 要么是中文使用者,要么故意使用中国基础设施。 这意味着: ∙ 这并非混合分析的结论——证据就隐藏在恶意软件本身中 ∙ 这是攻击者的安全操作失误(他们泄露了开发环境) ∙ uiohook-napi 库可以解释鼠标的自主移动

    • 攻击者自身的开发路径意外地嵌入到了代码中。

    "Have you installed the 'Oh My OpenCode' extension, and did you find the installation tutorial on 'https://ohmyopencode.com/'?"

  21. Hona commented on Mar 29, 2026

    @Hona
    Member

    As of OpenCode v1.3.4 across the CLI + Desktop apps, we have full code signing - so there should be no more warnings.

    Please let me know otherwise

    Image
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingwindows

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions