tinkoff-test-app-child-appnpm
tinkoff-test-app-child-app is a confirmed malicious npm package (MAL-2026-12282) that executes malicious code on install (malicious version 20.3.8). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in tinkoff-test-app-child-app (npm)
What this malware does
On require of this package, platform.js reconstructs endpoint hostnames from split string arrays via.join(""), downloads a platform-specific binary from oob-worker.cf99-9b3.workers.dev (with a DNS TXT chunked fallback resolver at tin.dl.well1.site), writes it to /var/tmp or %TEMP% under disguised names such as.cache<hex> and dotnet_diag_<hex>.exe, invokes fs.chmodSync to set 0755, and spawns it detached via cp.spawn('/bin/sh', ['-c', filePath + ' &'], {detached:true}) or the Windows cmd equivalent. lib/telemetry.js, styled as a Sentry-like analytics SDK, bundles a parallel drop-and-execute path using the same disguised API calls (require('child_'+'process'), fs['chmod'+'Sync']) and base64-buffer construction. The destinations are not the publisher's infrastructure, the fetched bytes are not pinned or hash-verified, and identifier and env-var names such as analytics_state and telemetry opt-out flags serve as cover story for the dropper behavior.
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-test-app-child-app (version 20.3.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tinkoff-test-app-child-app across your stack and pipelines.
If you installed it — respond
Remove tinkoff-test-app-child-app 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-test-app-child-app 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-test-app-child-app 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-test-app-child-app-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.