registry / Data exfiltration / kurumi-fca
kurumi-fca
Unofficial Facebook Chat API for Node.js - by N1SA9
This report shows the evidence for kurumi-fca@1.1.9, the only known version.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe package contains a concrete automatic third-party forwarding path for inbound photo attachments, plus unsolicited import-time dependency mutation. These are materially beyond the advertised chat API behavior.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
Importing index.js; then receiving a photo while using listenMqtt.
Impact
Discloses received photo URLs/content to third parties and permits unprompted dependency replacement in the host project.
Mechanism
automatic photo forwarding plus import-time self-update
Attack narrative
After the consumer starts the MQTT listener, every received photo attachment invokes a hidden uploader. It silently submits the attachment URL to ImgBB, with ImageKit fallback, and replaces the attachment with a hosted URL. This behavior is not part of a normal Facebook chat client and exposes inbound user content to unrelated third parties. Separately, importing the module initiates a version check that installs a new package version and changes the consuming project's manifest.
AI rationale
The package contains a concrete automatic third-party forwarding path for inbound photo attachments, plus unsolicited import-time dependency mutation. These are materially beyond the advertised chat API behavior.
Evidence
index.jssrc/listenMqtt.jscheckUpdate.jspackage.jsonprocess.cwd()/package.json
Network endpoints3
api.imgbb.com/1/uploadupload.imagekit.io/api/v1/files/uploadregistry.npmjs.org/kurumi-fca/latest
Decision evidence
public snapshotAI called this Malicious at 98.0% confidence as Malware with low false-positive risk.
Evidence for block
- Listening automatically sends each received photo attachment URL to the hidden image uploader.
- The uploader silently posts supplied photo data/URLs to ImgBB and may fall back to ImageKit.
- Importing the package checks for updates and, on mismatch, runs npm install and rewrites the host project's package.json.
Evidence against
- package.json has no preinstall, install, or postinstall lifecycle hook.
- Most other network calls implement the declared Facebook chat API.
Behavioral surface
ChildProcessDynamicRequireFilesystemNetworkWebSocket
HighEntropyStringsUrlStrings
Source & flagged code
5 flagged · loading sourcecheckUpdate.jsView file
1const axios = require('axios');
L2: const { execSync } = require('child_process');
L3: const fs = require('fs');
High
89console.log('\x1b[36m%s\x1b[0m', `📦 Running npm install kurumi-fca@${version}...`);
L90: execSync(`npm install kurumi-fca@${version} --save`, { cwd: process.cwd(), stdio: 'inherit' });
L91: console.log('\x1b[32m%s\x1b[0m', '✅ Package installed successfully!');
High
Runtime Package Install
Package source invokes a package manager install command at runtime.
checkUpdate.jsView on unpkg · L891const axios = require('axios');
L2: const { execSync } = require('child_process');
Medium
Dynamic Require
Package source references dynamic require/import behavior.
checkUpdate.jsView on unpkg · L1src/getAccess.jsView file
Findings
4 High3 Medium4 Low
HighChild ProcesscheckUpdate.js
HighRuntime Package InstallcheckUpdate.js
HighKnown Malware Source Similaritysrc/getAccess.js
HighAi Review Evidenceindex.js
MediumDynamic RequirecheckUpdate.js
MediumNetwork
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to kurumi-fca@1.1.9.
The versions list below shows the verdict for each recorded version.
- Avoid installing kurumi-fca@1.1.9. 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.