Which versions of checkout-mobile-promocode are malicious?

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

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

checkout-mobile-promocode is a typosquat — you almost certainly intended a legitimately-named package. Remove checkout-mobile-promocode, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed checkout-mobile-promocode — how do I know if it already compromised me?

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

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

Malicious package

checkout-mobile-promocodenpm

checkout-mobile-promocode is a confirmed malicious npm package (MAL-2026-12579) that typosquats a legitimate package to trick installs (malicious version 35.6.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in checkout-mobile-promocode (npm)

MAL-2026-12579

Immediate action

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

npm uninstall checkout-mobile-promocode

What this malware does

On require, index.js loads vendor.js which reconstructs destination hostnames from split string literals (e.g. ["oob-worker.c","f102-baf.worker","s.dev"].join("") and ['sdk.d','l.w','el1.ru'].join("")) to hide them from static inspection. It selects a platform-specific asset, downloads an unpinned, unverified executable from one of several *.workers.dev endpoints, falling back to DNS TXT base64 chunks under *.dl.wel1.ru (sdk/ext/pkg/net.dl.wel1.ru), writes it to /var/tmp or %TEMP% under a disguised name such as dotnet_diag.exe or.cache_, sets mode 0755 via fs.chmodSync, and spawns it detached via cp.spawn("/bin/sh",["-c", fp+" &"], {detached:true}) or cmd.exe. A sibling file lib/telemetry.js contains a structurally identical fetch-decode-chmod-spawn payload using require("child_"+"process") and fs["chmod"+"Sync"], packaged as an "analytics SDK" variant of the same dropper. The package name mimics a legitimate mobile-checkout/promo-code component but its only on-import effect is delivery and execution of attacker-controlled native code.

Malicious versions

1 flagged

35.6.9

Indicators of compromise (SHA-256)

f8b1a15a2100e63737bf9fdc85ec750761a4e58b07f961d8a5734a6f99626026

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for checkout-mobile-promocode (version 35.6.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging checkout-mobile-promocode across your stack and pipelines.
If you installed it — respond
checkout-mobile-promocode is a typosquat — you almost certainly intended a legitimately-named package. Remove checkout-mobile-promocode, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If checkout-mobile-promocode 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-promocode 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-promocode on npm has been identified as a malicious package (version 35.6.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015197

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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