@coopeuch/button
Coordinated vulnerability disclosure proof of concept for a dependency confusion issue.
This report shows the evidence for @coopeuch/button@1.999.999. 1 of 3 known versions is blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe manifest automatically runs a hook that collects identifying host and consumer-project information and sends it to an external endpoint without an activation or consent guard. This is concrete install-time data exfiltration, so the package should be blocked.
Decision evidence
public snapshot- The package runs postinstall.js automatically during installation.
- The hook assembles host, user, network, runtime, CI, and consumer project details into a report.
- The hook sends the report by HTTPS to collector.oob.s4yhii.com and also performs a DNS lookup to that domain.
- The source shows no shell execution, file writes, or persistence in the inspected hook.
Source & flagged code
7 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgThe package runs postinstall.js automatically during installation.
package.jsonView on unpkg · L10Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to @coopeuch/button@1.999.999.
The versions list below shows the verdict for each recorded version.
- Avoid installing @coopeuch/button@1.999.999. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.