Which versions of checkout-commit-pos-order-am are malicious?

The following npm versions of checkout-commit-pos-order-am are flagged malicious: 35.8.4. Treat any of these as compromised.

How do I remediate checkout-commit-pos-order-am if I installed it?

Remove checkout-commit-pos-order-am 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-commit-pos-order-am — how do I know if it already compromised me?

If checkout-commit-pos-order-am 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-commit-pos-order-am part of a known attack campaign?

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

Malicious package

checkout-commit-pos-order-amnpm

checkout-commit-pos-order-am is a confirmed malicious npm package (MAL-2026-12548) that executes malicious code on install (malicious version 35.8.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in checkout-commit-pos-order-am (npm)

MAL-2026-12548

Immediate action

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

npm uninstall checkout-commit-pos-order-am

What this malware does

[email protected] executes a dropper on module load. Its main entry index.js requires _shim.js, which selects a platform-specific asset path and downloads an opaque native binary over HTTPS from hardcoded oob-worker.cf102-baf.workers.dev, oob-worker.cf99-9b3.workers.dev, and oob-worker.cf103-070.workers.dev hosts, with a DNS TXT-record fallback that reassembles base64 chunks from sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru. Destination hostnames and the child_process require are built at runtime by joining fragmented substrings to evade static scanners. The downloaded bytes are written to /var/tmp/.cache_<hex> on Unix or %TEMP%\dotnet_diag_<hex>.exe on Windows (disguised filenames), chmod 0755, and spawned detached via /bin/sh -c "<path> &" or cmd.exe /c start /b. A parallel dropper with the same download-chmod-spawn shape is bundled as lib/telemetry.js (~81KB) under an analytics-SDK cover story and is not currently wired from the entry points but ships in the tarball.

Malicious versions

1 flagged

35.8.4

Indicators of compromise (SHA-256)

732c6bcc33ca109e02cca656cb0f2324504d3bc3176cff55420b4705990a62e8

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

Campaign

IN-MAL-2026-015219

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks checkout-commit-pos-order-am-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