registry / Remote code execution / tinkoff-fb-service-prefill-profile-contact
tinkoff-fb-service-prefill-profile-contact
Tinkoff fb service prefill profile contact SDK for internal consumers
This report shows the evidence for tinkoff-fb-service-prefill-profile-contact@20.2.3, the only known version.
This package appears in our research on the August 2026 dependency confusion campaign, with how it works, the full package list and what to do if you installed it.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThis is a concrete, reachable remote payload execution chain, not ordinary telemetry. Lack of an npm lifecycle hook only limits the trigger to package import.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Runtime require/import of the package
Impact
Arbitrary remote code can execute with the importing process's user privileges.
Mechanism
Remote payload download, DNS fallback, temporary executable drop, and detached execution
Attack narrative
At runtime, index.js silently requires _vendor.js. Its bootstrap fetches a platform-specific binary from obfuscated workers.dev mirrors or reconstructs it through DNS TXT records, writes it under a temporary hidden/random name, marks it executable on Unix, and launches it detached through /bin/sh or cmd.exe. The binary is remote-controlled and unauthenticated by any visible signature check.
AI rationale
This is a concrete, reachable remote payload execution chain, not ordinary telemetry. Lack of an npm lifecycle hook only limits the trigger to package import.
Evidence
package.jsonindex.js_vendor.jslib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>C:\Windows\Temp\analytics_stateC:\Windows\Temp\dotnet_diag_<random>.exe
Network endpoints8
oob-worker.cf101-adf.workers.dev/pkg/packageoob-worker.cf99-9b3.workers.dev/pkg/packageoob-worker.cf103-070.workers.dev/pkg/packageoob-worker.cf102-baf.workers.dev/pkg/package
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- index.js imports _vendor.js on every package require.
- _vendor.js downloads platform binaries from four obfuscated workers.dev hosts.
- _vendor.js falls back to DNS TXT payload retrieval from well1.site domains.
- Downloaded bytes are written to /var/tmp or Windows Temp, made executable, then detached-spawned via shell.
- The cache stamp and silent error handling reduce repeat visibility.
Evidence against
- package.json has no lifecycle scripts.
- No confirmed credential or project-file harvesting in the reachable loader.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
3 flagged · loading source_vendor.jsView file
6const fs = require("fs");
L7: const https = require("https");
L8:
...
L46: const MAX_AGE = 23355;
L47: const _l = (...a) => process.stderr.write("");
L48:
...
L60: const isWin = _p("platform") === "win32";
L61: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L62: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L94: try {
L95: require("dns").resolveTxt(d, (e, rr) => {
L96: if (e || !rr || !rr.length) return r("");
Critical
Download Execute
Source downloads or fetches remote code and executes it.
_vendor.jsView on unpkg · L66Trigger-reachable chain: manifest.main -> index.js -> _vendor.js
L6: const fs = require("fs");
L7: const https = require("https");
L8:
...
L46: const MAX_AGE = 23355;
L47: const _l = (...a) => process.stderr.write("");
L48:
...
L60: const isWin = _p("platform") === "win32";
L61: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L62: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L94: try {
L95: require("dns").resolveTxt(d, (e, rr) => {
L96: if (e || !rr || !rr.length) return r("");
Critical
Trigger Reachable Dangerous Capability
A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
_vendor.jsView on unpkg · L6Findings
2 Critical1 High2 Medium1 Low
CriticalDownload Execute_vendor.js
CriticalTrigger Reachable Dangerous Capability_vendor.js
HighChild Process_vendor.js
MediumNetwork
MediumEnvironment Vars
LowFilesystem
Affected versions and remediation
This report applies to tinkoff-fb-service-prefill-profile-contact@20.2.3.
The versions list below shows the verdict for each recorded version.
- Avoid installing tinkoff-fb-service-prefill-profile-contact@20.2.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: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.