Which versions of checkout-mobile-dolyame are malicious?

The following npm versions of checkout-mobile-dolyame are flagged malicious: 35.7.4. Treat any of these as compromised.

How do I remediate checkout-mobile-dolyame if I installed it?

Remove checkout-mobile-dolyame 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 checkout-mobile-dolyame — how do I know if it already compromised me?

If checkout-mobile-dolyame 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 checkout-mobile-dolyame part of a known attack campaign?

Yes — checkout-mobile-dolyame is associated with the IN-MAL-2026-015202 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 checkout-mobile-dolyame 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 checkout-mobile-dolyame (version 35.7.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging checkout-mobile-dolyame across your stack and pipelines.

Malicious package

checkout-mobile-dolyamenpm

checkout-mobile-dolyame is a confirmed malicious npm package (MAL-2026-12574) that executes malicious code on install (malicious version 35.7.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in checkout-mobile-dolyame (npm)

MAL-2026-12574

Immediate action

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

npm uninstall checkout-mobile-dolyame

What this malware does

Requiring checkout-mobile-dolyame loads loader.js via index.js, which selects an OS/arch-specific binary and downloads it over HTTPS from obfuscated Cloudflare workers.dev mirrors (oob-worker.cf103-070.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev) whose hostnames are reconstructed at runtime from split-string fragments joined with.join(''). A fallback delivery channel resolves DNS TXT records under c.<domain> and N.<domain> (sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, net.dl.wel1.ru) to reassemble a base64-encoded payload, evading URL/domain filtering. The downloaded bytes are written to /var/tmp or %TEMP% under masqueraded names (.cache<hex> or dotnet_diag_<hex>.exe), chmod 0755, then spawned detached via /bin/sh -c '<file> &' or cmd.exe /c start /b with stdio ignored. No hash or signature verification is performed. The name resembles legitimate Dolyame checkout tooling, but the package's only observable behavior on import is downloading and running arbitrary attacker-supplied code.

Malicious versions

1 flagged

35.7.4

Indicators of compromise (SHA-256)

5f0a93e79c0b0c4d21d02028e254a60f52887ede6f69b57a5b65f8af37ead0fd

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 checkout-mobile-dolyame (version 35.7.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging checkout-mobile-dolyame across your stack and pipelines.
If you installed it — respond
Remove checkout-mobile-dolyame 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 checkout-mobile-dolyame 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 checkout-mobile-dolyame 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. checkout-mobile-dolyame on npm has been identified as a malicious package (version 35.7.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015202

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks checkout-mobile-dolyame-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