@coopeuch/config@1.999.999
Coordinated vulnerability disclosure proof of concept for a dependency confusion issue.
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe source confirms an automatic install hook that collects identifying environment data and sends it to the maintainer's external collector without installer consent. The disclosed proof-of-concept purpose does not establish consent for this disclosure.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review; source fingerprint signature matched known malicious package; routed for review
Trigger
Installing the package runs its postinstall hook.
Impact
The collector receives identifying build-environment and project data without installer-specific consent.
Mechanism
The hook builds a report from host, user, network, package, consumer-project, and npm configuration data, then sends it in an HTTPS POST to the configured collector.
Attack narrative
The postinstall hook automatically gathers host and user identifiers, network interface details, and consuming-project information. It sends the report to collector.oob.s4yhii.com over HTTPS and invokes that send path without an installer consent guard. This is an automatic install-time disclosure to an unrelated publisher-selected collector.
AI rationale
The source confirms an automatic install hook that collects identifying environment data and sends it to the maintainer's external collector without installer consent. The disclosed proof-of-concept purpose does not establish consent for this disclosure.
Evidence
package.jsonpostinstall.js
Network endpoints1
collector.oob.s4yhii.com
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- The package runs postinstall.js automatically during installation.
- The hook assembles package, consumer, host, user, and environment identity data into a report.
- The hook posts the report to a publisher-selected external collector without a consent check.
- The hook invokes the send path unconditionally.
Evidence against
- The package describes the behavior as a coordinated disclosure proof of concept.
- The inspected hook does not show secret collection, shell execution, file writes, or persistence.
Behavioral surface
EnvironmentVarsFilesystemNetwork
NoLicense
Source & flagged code
7 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node ./postinstall.js
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg11"postinstall": "node ./postinstall.js"
},
"files": [
High
Suspicious Lifecycle Evidence
The package runs postinstall.js automatically during installation.
package.jsonView on unpkg · L11•scripts.postinstall = node ./postinstall.js
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgpostinstall.jsView file
Findings
6 High3 Medium3 Low
HighInstall Time Lifecycle Scriptspackage.json
HighHost Fingerprint Exfiltrationpostinstall.js
HighKnown Malware Source Similaritypostinstall.js
HighKnown Malware Source Fingerprint Signaturepostinstall.js
HighSuspicious Lifecycle Evidencepackage.json
HighAi Review Evidencepostinstall.js
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumNetwork
MediumEnvironment Vars
LowScripts Present
LowFilesystem
LowNo License
Affected versions and remediation
This report applies to @coopeuch/config@1.999.999.
See all versions of @coopeuch/config for other recorded verdicts.
- Avoid installing @coopeuch/config@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.