Which versions of tinkoff-mutual-mgm-form are malicious?

The following npm versions of tinkoff-mutual-mgm-form are flagged malicious: 20.2.9. Treat any of these as compromised.

How do I remediate tinkoff-mutual-mgm-form if I installed it?

Remove tinkoff-mutual-mgm-form 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.

I already installed tinkoff-mutual-mgm-form — how do I know if it already compromised me?

If tinkoff-mutual-mgm-form 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.

Is tinkoff-mutual-mgm-form part of a known attack campaign?

Yes — tinkoff-mutual-mgm-form is associated with the IN-MAL-2026-014513 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find tinkoff-mutual-mgm-form across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for tinkoff-mutual-mgm-form (version 20.2.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tinkoff-mutual-mgm-form across your stack and pipelines.

Malicious package

tinkoff-mutual-mgm-formnpm

tinkoff-mutual-mgm-form is a confirmed malicious npm package (MAL-2026-12244) that executes malicious code on install (malicious version 20.2.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tinkoff-mutual-mgm-form (npm)

MAL-2026-12244

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall tinkoff-mutual-mgm-form

What this malware does

On require('tinkoff-mutual-mgm-form'), index.js loads compat.js, which selects a platform-specific asset path and fetches a native binary over HTTPS from Cloudflare Workers subdomains assembled via array.join('') string concatenation (oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev), with a DNS TXT chunked fallback to look-alike hosts under dl.well1.site (tin.dl.well1.site, tina.dl.well1.site, ldr.dl.well1.site, win.dl.well1.site). The fetched bytes are written to a masquerading path in /var/tmp or %TEMP% (e.g., dotnet_diag<rnd>.exe or.cache_<rnd>), chmodded to 0755, and spawned detached via /bin/sh -c '<path> &' or cmd.exe start /b. The require('child_process') module name is also split-string obfuscated, and cover-story comments frame the behavior as 'telemetry' and 'session tracking'. A second copy of the same fetch-write-chmod-spawn dropper is bundled in lib/telemetry.js as an 'Analytics SDK', staged as an alternate payload. Destinations, obfuscation, masquerading filenames, and detached execution are inconsistent with the package's declared purpose.

Malicious versions

1 flagged

20.2.9

Indicators of compromise (SHA-256)

84bc64dc52d6f64a0673f548b3201cc6eed96ea71665ccd1fc1a41b29ac12cca

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for tinkoff-mutual-mgm-form (version 20.2.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tinkoff-mutual-mgm-form across your stack and pipelines.
If you installed it — respond
Remove tinkoff-mutual-mgm-form 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-mutual-mgm-form 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-mutual-mgm-form 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

No. tinkoff-mutual-mgm-form on npm has been identified as a malicious package (version 20.2.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014513

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks tinkoff-mutual-mgm-form-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database