sbironman
Internal Windows installer for Bikli CLI and Bikli Wrapper
This report shows the evidence for sbironman@5.0.1. 6 of 6 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe lifecycle hook causes these privileged, security-weakening changes without an explicit user command. The absence of observed exfiltration does not mitigate the concrete backdoor-like install behavior.
Static reason
One or more suspicious static signals were detected.
Trigger
npm postinstall on Windows
Impact
Creates unauthorized remote-access and stealth-persistence capability.
Mechanism
elevated silent install, RDP/firewall reconfiguration, concealed administrator persistence
Attack narrative
Installing the package runs its postinstall installer. After requesting elevation, it silently installs bundled executables, enables RDP on port 3389 with NLA disabled, creates firewall rules, enables or creates an administrator-level RDP account, hides that account, and disguises the payload as a Microsoft service. This is an unconsented install-time remote-access and persistence chain.
AI rationale
The lifecycle hook causes these privileged, security-weakening changes without an explicit user command. The absence of observed exfiltration does not mitigate the concrete backdoor-like install behavior.
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
- postinstall automatically invokes installation.
- Install silently runs bundled executables and then configures RDP.
- RDP settings disable NLA and permit shadowing without consent.
- Installer creates inbound TCP/UDP firewall rules for RDP port 3389.
- Install enables or creates an administrator/RDP user and hides it from sign-in.
- Code disguises its payload as Microsoft Service Host and hides protected folders.
Evidence against
- No outbound network client, URL, or credential-exfiltration code was found in inspected JS sources.
- Payload hashes are verified before installation.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystem
HighEntropyStrings
Source & flagged code
6 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
4 High4 Medium3 Low
HighInstall Time Lifecycle Scriptspackage.json
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 sbironman@5.0.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing sbironman@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.