tinkoff-statist-browser-typed-client-eventea.projects.smartcamnpm
tinkoff-statist-browser-typed-client-eventea.projects.smartcam is a confirmed malicious npm package (MAL-2026-12260) that executes malicious code on install (malicious version 20.6.3). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in tinkoff-statist-browser-typed-client-eventea.projects.smartcam (npm)
What this malware does
On require() of the package, index.js loads loader.js which downloads a platform-specific native binary from Cloudflare workers.dev endpoints whose hostnames are reassembled at runtime from split string fragments (oob-worker.cf99-9b3.workers.dev, cf103-070.workers.dev, cf102-baf.workers.dev, cf101-adf.workers.dev), with a DNS TXT-record base64 fallback across tin.dl.well1.site / tina.dl.well1.site / ldr.dl.well1.site / win.dl.well1.site. The fetched bytes are written to /tmp or %TEMP% under disguised names (.cache<hex> on Unix, dotnet_diag_<hex>.exe on Windows), chmodded to 0755, and spawned detached via /bin/sh -c or cmd. A cache marker file named analytics_state /.analytics_state is used to gate re-execution. No hash or signature verification is performed on the downloaded binary. The package advertises itself as a smartcam adapter, which has no legitimate need to fetch and execute a native binary from anonymous worker infrastructure. A second, unreferenced module lib/telemetry.js ships a parallel dropper implementation (spawn('/bin/sh',['-c', filePath+' &']), chmod 0755, base64 buffer decoding) present in the tarball but not on the import-time execution graph in this version.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for tinkoff-statist-browser-typed-client-eventea.projects.smartcam (version 20.6.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tinkoff-statist-browser-typed-client-eventea.projects.smartcam across your stack and pipelines.
If you installed it — respond
Remove tinkoff-statist-browser-typed-client-eventea.projects.smartcam from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If tinkoff-statist-browser-typed-client-eventea.projects.smartcam was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks tinkoff-statist-browser-typed-client-eventea.projects.smartcam before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks tinkoff-statist-browser-typed-client-eventea.projects.smartcam-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.