NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

tinkoff-mutual-mgm-formnpm

Advisory published Updated

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.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged
20.2.9

Indicators of compromise (SHA-256)

84bc64dc52d6f64a0673f548b3201cc6eed96ea71665ccd1fc1a41b29ac12cca
e7a647d16757b3c13766a43736e8a5e756ec4203bdfbcd48c570e344239f9242

Detection & response playbook

Malicious package

  1. Find it

    Search your lockfiles and build artifacts for tinkoff-mutual-mgm-form (version 20.2.9).

  2. 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.

  3. Did it already run?

    If tinkoff-mutual-mgm-form was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

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-014513GHSA-6q5q-68cm-4f3c

References

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
tinkoff-mutual-mgm-form (npm) malicious package — MAL-2026-12244 | O3 Security