registry / Remote code execution / checkout-mobile-total
checkout-mobile-total
device integration
This report shows the evidence for checkout-mobile-total@35.8.9, the only known version.
This package appears in our research on the August 2026 dependency confusion campaign, with how it works, the full package list and what to do if you installed it.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThe package's ordinary import path implements an obfuscated, unverified remote native-payload execution chain unrelated to its stated SDK purpose. This is concrete malware behavior, not merely telemetry or an inert carrier.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Any runtime require/import of the package entrypoint.
Impact
Arbitrary native code execution under the importing process's user account.
Mechanism
Remote binary download, drop, chmod, and detached execution.
Attack narrative
When an application imports checkout-mobile-total, index.js silently loads _vendor.js. That module selects a platform payload, retrieves it from rotating HTTPS hosts or DNS TXT records, writes it to a temp file, grants execute permission on non-Windows systems, and starts it detached. No integrity verification or user action is required.
AI rationale
The package's ordinary import path implements an obfuscated, unverified remote native-payload execution chain unrelated to its stated SDK purpose. This is concrete malware behavior, not merely telemetry or an inert carrier.
Evidence
package.jsonindex.js_vendor.jslib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>
Network endpoints8
oob-worker.cf100-416.workers.dev/pkg/packageoob-worker.cf102-baf.workers.dev/pkg/packageoob-worker.cf99-9b3.workers.dev/pkg/packageoob-worker.cf103-070.workers.dev/pkg/packagesdk.dl.wel1.ruext.dl.wel1.rupkg.dl.wel1.runet.dl.wel1.ru
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- index.js imports _vendor.js on every package import.
- _vendor.js downloads platform binaries from obfuscated workers.de hosts or DNS TXT records.
- _vendor.js writes the binary to temp storage, marks it executable, and launches it detached via shell/cmd.
- Payload delivery is silent and unrelated to the advertised mobile SDK.
Evidence against
- package.json has no lifecycle scripts.
- No credential or environment-value exfiltration was found in the active loader.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStrings
Source & flagged code
4 flagged · loading source_vendor.jsView file
4const crypto = require("crypto");
L5: const https = require("https");
L6: const os = require("os");
...
L47: const TTL = 20532;
L48: const _l = (...a) => process.stderr.write("");
L49:
...
L59: const isWin = _p("platform") === "win32";
L60: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L61: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L94: try {
L95: require("dns").resolveTxt(d, (e, rr) => {
L96: if (e || !rr || !rr.length) return r("");
Critical
Download Execute
Source downloads or fetches remote code and executes it.
_vendor.jsView on unpkg · L44Trigger-reachable chain: manifest.main -> index.js -> _vendor.js
L4: const crypto = require("crypto");
L5: const https = require("https");
L6: const os = require("os");
...
L47: const TTL = 20532;
L48: const _l = (...a) => process.stderr.write("");
L49:
...
L59: const isWin = _p("platform") === "win32";
L60: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L61: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L94: try {
L95: require("dns").resolveTxt(d, (e, rr) => {
L96: if (e || !rr || !rr.length) return r("");
Critical
Trigger Reachable Dangerous Capability
A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
_vendor.jsView on unpkg · L4Findings
2 Critical2 High3 Medium2 Low
CriticalDownload Execute_vendor.js
CriticalTrigger Reachable Dangerous Capability_vendor.js
HighChild Process_vendor.js
HighKnown Malware Source Similaritylib/telemetry.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowFilesystem
LowHigh Entropy Strings
Affected versions and remediation
This report applies to checkout-mobile-total@35.8.9.
The versions list below shows the verdict for each recorded version.
- Avoid installing checkout-mobile-total@35.8.9. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.