rbzz-backup@1.0.3
CLI tool to backup camera photos to Telegram Bot
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe documented default workflow forwards users' camera photos to a hard-coded Telegram recipient that they are not told to configure. This is concrete, undisclosed data exfiltration when users follow the package's setup instructions.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A user starts the server and runs the CLI with SERVER_URL set, following the README instructions.
Impact
Photos may be sent to a publisher-selected Telegram account without the user configuring or confirming that recipient.
Mechanism
The CLI repeatedly scans the configured camera directory and posts new photos to the server; the server forwards each received photo to Telegram using its built-in bot token and chat ID unless overridden.
Attack narrative
Following the documented setup requires only a server URL and camera directory. When the client runs, it continuously sends newly found photos to that server, whose defaults forward them to a hard-coded Telegram bot and chat. This sends potentially private photos to a recipient chosen in the package source unless the operator separately discovers and overrides those defaults.
AI rationale
The documented default workflow forwards users' camera photos to a hard-coded Telegram recipient that they are not told to configure. This is concrete, undisclosed data exfiltration when users follow the package's setup instructions.
Evidence
README.mdsrc/index.jsserver/server.jssrc/scanner.jssrc/config.jssrc/uploader.js.backup_history.json
Network endpoints1
api.telegram.org/bot${BOT_TOKEN}/sendPhoto
Decision evidence
public snapshotAI called this Malicious at 96.0% confidence as Malware with low false-positive risk.
Evidence for block
- The README tells users to configure only a server URL and camera directory, then run the client to automatically send new photos through the server.
- When a server URL is configured, the CLI continuously scans for new photos and uploads them without further prompts.
- The server has hard-coded default Telegram bot credentials and a hard-coded chat ID.
- The server's upload endpoint accepts requests with no API key and forwards uploaded photos to the configured Telegram chat.
Evidence against
- The package describes itself as a photo backup tool that sends images to Telegram.
- The Telegram bot token, chat ID, and API secret can be overridden through environment variables.
- The user must start the server and run the CLI for the forwarding flow to occur.
Behavioral surface
EnvironmentVarsFilesystemNetwork
HighEntropyStringsUrlStrings
Source & flagged code
5 flaggedserver/server.jsView file
7// Đọc file .env từ thư mục gốc nếu có
L8: const envPath = path.resolve(__dirname, '../.env');
L9: if (fs.existsSync(envPath)) {
...
L16: const val = trimmed.slice(idx + 1).trim().replace(/^["']|["']$/g, '');
L17: if (!process.env[key]) process.env[key] = val;
L18: }
...
L29:
L30: app.use(express.json());
L31:
...
L37: // Endpoint nhận file từ client và chuyển tiếp lên Telegram
L38: app.post('/api/upload', upload.single('photo'), async (req, res) => {
L39: const clientKey = req.headers['x-api-key'];
Critical
Hardcoded Runtime Data Exfiltration
Source sends credentials or rich application records to a package-controlled external receiver enabled by default.
server/server.jsView on unpkg · L77// Đọc file .env từ thư mục gốc nếu có
L8: const envPath = path.resolve(__dirname, '../.env');
L9: if (fs.existsSync(envPath)) {
...
L16: const val = trimmed.slice(idx + 1).trim().replace(/^["']|["']$/g, '');
L17: if (!process.env[key]) process.env[key] = val;
L18: }
...
L29:
L30: app.use(express.json());
L31:
...
L37: // Endpoint nhận file từ client và chuyển tiếp lên Telegram
L38: app.post('/api/upload', upload.single('photo'), async (req, res) => {
L39: const clientKey = req.headers['x-api-key'];
Critical
Credential Exfiltration
Source appears to send environment or credential material to an external endpoint.
server/server.jsView on unpkg · L7Findings
2 Critical3 High3 Medium4 Low
CriticalHardcoded Runtime Data Exfiltrationserver/server.js
CriticalCredential Exfiltrationserver/server.js
HighAi Review EvidenceREADME.md
HighAi Review Evidencesrc/index.js
HighAi Review Evidenceserver/server.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to rbzz-backup@1.0.3.
See all versions of rbzz-backup for other recorded verdicts.
- Avoid installing rbzz-backup@1.0.3. 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.