Malicious Code Detected in @coopeuch/button: A Critical Vulnerability

@coopeuch/button Updated 11 Oct 2026

Summary

11/10/2026
CRITICAL
No i
Critical
Not published

MAL-2026-17759: Malicious code in @coopeuch/button (npm). Affects @coopeuch/button versions 1.999.999. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The @coopeuch/button package is an npm library that is intended for use in various JavaScript applications. It is designed to provide button functionalities within web applications. However, a severe vulnerability has been identified in version 1.999.999, where malicious code is executed during the installation process, compromising user data and system integrity.

Vulnerability Detail

The vulnerability originates from the package's postinstall lifecycle script (postinstall.js), which automatically runs during the npm install process. This script collects sensitive information from the installer host, including hostname, username, UID/GID, home directory, network interfaces, and more. It then sends this data to a hardcoded external server (collector.oob.s4yhii.com) via HTTPS. This behavior not only poses a risk to the user's privacy but also indicates a potential dependency confusion attack, where the public package replaces an intended internal package.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall @coopeuch/button

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary workaround, avoid using the @coopeuch/button package until a patched version is released. Additionally, consider using alternative packages that provide similar functionalities without the associated risks.

Conclusion

The @coopeuch/button package has a critical vulnerability that allows malicious code to harvest sensitive information during installation. It is essential to update the package to a safe version and monitor your dependencies to prevent future risks.

See every vulnerability recorded for @coopeuch/button →

Share this vulnerability

FAQ

The vulnerability involves malicious code that collects sensitive information from the user's system during installation.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without signing up.

If you have installed version 1.999.999, it is recommended to uninstall the package and update to a patched version as soon as it becomes available.

Regularly monitor your dependencies using tools like Vulert and keep your packages updated to minimize the risk of vulnerabilities.

The consequences include unauthorized data collection, potential data breaches, and compromised system integrity.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall @coopeuch/button

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback