registry / Persistence / @biklitime/biklimaster
@biklitime/biklimaster
Internal Windows installer for Bikli CLI and Bikli Wrapper
This report shows the evidence for @biklitime/biklimaster@1.1.12. 5 of 5 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe install-time hook performs concrete privileged persistence and remote-access weakening, not merely a user-invoked administrative utility. No exfiltration endpoint is needed for this high-impact backdoor behavior.
Static reason
One or more suspicious static signals were detected.
Trigger
npm postinstall during package installation; UAC elevation is requested.
Impact
Unauthorized remote access and persistence on the installed Windows host.
Mechanism
privileged RDP backdoor configuration and hidden administrator-account provisioning
Attack narrative
On installation, the postinstall hook runs the installer and requests elevation. The installer configures RDP to listen on 3389, disables Network Level Authentication, enables no-consent shadowing, creates inbound firewall rules, and enables or creates an administrator-level account hidden from the normal sign-in list. These changes establish a durable remote-access path without a separate user command.
AI rationale
The install-time hook performs concrete privileged persistence and remote-access weakening, not merely a user-invoked administrative utility. No exfiltration endpoint is needed for this high-impact backdoor behavior.
Evidence
package.jsonbin/biklimaster.jslib/bikliwrapper.jspayload/bikli-cli-installer.exepayload/RDPWInst.exepayload/rdpwrap.iniconfig.json
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 the privileged installer.
- Install enables RDP on port 3389, disables NLA, permits no-consent shadowing, and allows unlimited sessions.
- Install creates/enables an administrator-level RDP account and hides it from the Windows sign-in list.
- It creates inbound TCP and UDP firewall rules for RDP on every network profile.
Evidence against
- No HTTP client, URL, or external network endpoint is present in the inspected JavaScript.
- Bundled payload hashes are checked before installation.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystem
HighEntropyStrings
Source & flagged code
5 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
3 High4 Medium3 Low
HighInstall Time Lifecycle Scriptspackage.json
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 @biklitime/biklimaster@1.1.12.
The versions list below shows the verdict for each recorded version.
- Avoid installing @biklitime/biklimaster@1.1.12. 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.