@coopeuch/core
Core utilities and shared module configuration.
This report shows the evidence for @coopeuch/core@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 automatic install hook transmits host and consumer-project identifying information to an external collector. This is a concrete data-exfiltration behavior, regardless of the source comments describing it as a proof of concept.
Decision evidence
public snapshot- The package runs postinstall.js automatically during installation.
- The hook gathers host, user, network, consumer-project, and runtime identity details into a report.
- The hook sends that report to an external collector and makes a package-labeled DNS lookup.
- The code labels the behavior a proof of concept and describes limits on collected data, but it still transmits identifying host and project details.
Source & flagged code
8 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgThe package runs postinstall.js automatically during installation.
package.jsonView on unpkg · L11Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to @coopeuch/core@1.999.999.
The versions list below shows the verdict for each recorded version.
- Avoid installing @coopeuch/core@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.