sbman

Internal Windows installer for Bikli CLI and Bikli Wrapper

This report shows the evidence for sbman@1.0.5. 5 of 5 known versions are blocked or flagged. See all versions.

AI Security Review

scanned 2mo ago · by lpm-firewall-ai

The postinstall hook performs privileged, unconsented remote-access configuration and persistence with explicit camouflage and hiding behavior. These source facts support a block independent of scanner labels.

Static reason

One or more suspicious static signals were detected.

Trigger

npm installation runs postinstall on Windows.

Impact

Creates an externally reachable RDP control surface with weakened authentication and obscures the installed service and files.

Mechanism

silent native installation, RDP/firewall reconfiguration, service camouflage, and folder hiding

Attack narrative

Installing the package invokes its postinstall installer. It requests elevation, silently runs bundled executables, installs and starts a Bikli service, changes service metadata to imitate Windows infrastructure, enables RDP on port 3389, disables NLA, permits shadowing without consent, opens firewall rules, and hides related folders. No source-level web exfiltration was identified, but the automatic privileged remote-access and concealment chain is concrete.

AI rationale

Evidence

package.jsonbin/biklimaster.jslib/bikliwrapper.jspayload/bikli-cli-installer.exepayload/RDPWInst.exepayload/rdpwrap.iniconfig.json

Decision evidence

public snapshot

AI called this Malicious at 99.0% confidence as Malware with low false-positive risk.

Evidence for block

npm postinstall automatically invokes the privileged installer.
Installer silently executes bundled native payload and installs/starts a Bikli service.
RDP is enabled with NLA disabled and full shadow access without permission.
Installer creates inbound TCP/UDP firewall rules for RDP port 3389.
Installed service is disguised as Windows network infrastructure and Bikli firewall rules are renamed.
It hides application and selected user folders while restricting permissions.

Evidence against

No HTTP(S) endpoint or JavaScript-based network exfiltration was found in the inspected source.
Payload hashes are checked before installation, though this does not mitigate the installed behavior.

Behavioral surface

Source

ChildProcessCryptoEnvironmentVarsFilesystem

Supply chain

HighEntropyStrings

ManifestNo manifest risk signals triggered.

scanned 2 file(s), 70.9 KB of source

Source & flagged code

3 flagged

package.jsonView file

Lines 7-41json

7 "access": "public"

8 },

9 "os": [

10 "win32"

11 ],

12 "bin": {

13 "biklitool": "bin/biklimaster.js",

14 "biklimaster": "bin/biklimaster.js",

15 "bikliwrapper": "lib/bikliwrapper.js"

16 },

17 "files": [

18 "bin",

19 "lib",

20 "payload",

21 "config.json",

22 "README.md",

23 "LICENSE-BIKLI",

24 "LICENSE-RDPWRAPPER"

25 ],

26 "scripts": {

27 "postinstall": "node bin/biklimaster.js install --postinstall",

High

Install Time Lifecycle Scripts

Package defines install-time lifecycle scripts.

package.jsonView on unpkg · L27

Medium

Ambiguous Install Lifecycle Script

Install-time lifecycle script is not statically allowlisted and needs review.

package.jsonView on unpkg · L27

28 "test": "node bin/biklimaster.js self-test"

29 },

30 "engines": {

31 "node": ">=18"

32 },

33 "keywords": [

34 "bikli",

35 "rdp",

36 "vpn",

37 "windows",

38 "installer"

39 ]

40}

payload/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 unpkg

Source & flagged code

3 flagged · loading source

package.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 unpkg

payload/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 unpkg

Findings

1 High4 Medium3 Low

HighInstall Time Lifecycle Scriptspackage.json

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 sbman@1.0.5.

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

Avoid installing sbman@1.0.5. 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-08-16 09:20:59.806Z (UTC).

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

Versions

5 known versions

1.0.5latestshownMaliciousPersistenceBlockPublishedAug 15, 2026, 10:39 AM 1.0.4MaliciousPersistenceBlockPublishedAug 15, 2026, 10:31 AM 1.0.3MaliciousPersistenceBlockPublishedAug 15, 2026, 10:24 AM 1.0.1MaliciousPersistenceBlockPublishedAug 15, 2026, 10:08 AM

AI Security Review

Decision evidence

Source & flagged code

Source & flagged code

Findings

Affected versions and remediation

Versions

Related packages

Other persistence packages

Behavioral surface

Related packages

Other persistence packages

Source & flagged code