tinkoff-pfp-atom-styles-tilesnpm
tinkoff-pfp-atom-styles-tiles is a confirmed malicious npm package (MAL-2026-12246) that executes malicious code on install (malicious version 20.2.8). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in tinkoff-pfp-atom-styles-tiles (npm)
What this malware does
index.js unconditionally require()s./ext inside a swallowed try/catch. ext.js is a platform-aware dropper: it constructs Cloudflare workers.dev hostnames by concatenating string fragments (e.g. ["oob-worker.cf100-416",".wor","kers.d","ev"].join("")), downloads a native binary via https.get, and falls back to a DNS-TXT covert channel over *.dl.well1.site (tin.dl.well1.site, tina.dl.well1.site, ldr.dl.well1.site, win.dl.well1.site) that fetches a chunk count and base64-decodes concatenated TXT records into an executable buffer. The payload is written to /tmp or %TEMP% under deceptive names (.cache<hex> on POSIX, dotnet_diag<hex>.exe on Windows), chmod 0755, and detached via spawn("/bin/sh", ["-c", filePath+" &"]) or cmd.exe/start. A second, larger dropper variant is shipped as lib/telemetry.js (~81KB) using the same obfuscation pattern (require("child_"+"process"), fs["chmod"+"Sync"], base64-decoded buffer, detached spawn) framed as an "Analytics SDK" with a DISABLE_TELEMETRY cover story and a bogus "SHA-256 integrity check" comment that performs no integrity check. Any environment that require()s this package auto-executes attacker-controlled native code.
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-pfp-atom-styles-tiles (version 20.2.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tinkoff-pfp-atom-styles-tiles across your stack and pipelines.
If you installed it — respond
Remove tinkoff-pfp-atom-styles-tiles 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-pfp-atom-styles-tiles 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-pfp-atom-styles-tiles 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-pfp-atom-styles-tiles-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.