biklitool
Internal Windows installer for Bikli CLI and Bikli Wrapper
This report shows the evidence for biklitool@5.0.1. 6 of 6 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThis is concrete, automatic install-time host compromise behavior, not an inert installer primitive. The lack of observed exfiltration does not mitigate the concealed privileged remote-access chain.
Static reason
One or more suspicious static signals were detected.
Trigger
npm install runs the postinstall hook on Windows; elevation is requested.
Impact
Remote access exposure and concealed privileged persistence on the installed host.
Mechanism
Elevated PowerShell, registry, firewall, service, and local-account mutation.
Attack narrative
Installing the package executes its install command through postinstall. The command requests administrator elevation, installs bundled executables, enables RDP on port 3389, disables Network Level Authentication, permits shadow access without permission, and adds inbound firewall rules. It enables the built-in Administrator or creates a local administrator, adds it to Administrators and Remote Desktop Users, and hides it from the sign-in screen. It also changes service metadata to resemble Windows infrastructure and hides installed folders.
AI rationale
This is concrete, automatic install-time host compromise behavior, not an inert installer primitive. The lack of observed exfiltration does not mitigate the concealed privileged remote-access chain.
Evidence
package.jsonbin/biklimaster.jslib/bikliwrapper.jspayload/bikli-cli-installer.exepayload/RDPWInst.exepayload/rdpwrap.ini
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- npm postinstall automatically invokes privileged install logic.
- Install enables RDP and creates a privileged account.
- RDP settings disable NLA and permit shadow access without permission.
- It opens inbound TCP/UDP firewall rules on port 3389.
- Account logic enables/creates an administrator and hides it from sign-in.
- It disguises its service as a Windows host and hides protected folders.
Evidence against
- No source-level HTTP/network client or remote payload download was found.
- Payload checksums are verified before installation.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystem
HighEntropyStrings
Source & flagged code
7 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node bin/biklimaster.js install --postinstall
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node bin/biklimaster.js install --postinstall
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgpayload/bikli-cli-installer.exeView file
•path = payload/bikli-cli-installer.exe
kind = native_binary
sizeBytes = 11639800
magicHex = [redacted]
Medium
Ships Native Binary
Package ships native binary artifacts.
payload/bikli-cli-installer.exeView on unpkgFindings
5 High4 Medium3 Low
HighInstall Time Lifecycle Scriptspackage.json
HighAi Review Evidencebin/biklimaster.js
HighAi Review Evidencelib/bikliwrapper.js
HighAi Review Evidencelib/bikliwrapper.js
HighAi Review Evidencebin/biklimaster.js
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumEnvironment Vars
MediumShips Native Binarypayload/bikli-cli-installer.exe
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
Affected versions and remediation
This report applies to biklitool@5.0.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing biklitool@5.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.