registry / Remote code execution / checkout-mobile-accounts
checkout-mobile-accounts
mobile SDK
This report shows the evidence for checkout-mobile-accounts@35.6.8, 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 malicious behavior is directly reachable on ordinary package import and executes unauthenticated remote content. No lifecycle hook is needed for the package to compromise an application process.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Any runtime require/import of checkout-mobile-accounts.
Impact
Arbitrary attacker-controlled code executes with the privileges of the importing process.
Mechanism
Import-time remote binary download, drop, chmod, and detached execution.
Attack narrative
Loading index.js silently requires _platform.js. That module fetches a platform-specific payload from obfuscated workers.dev mirrors, falling back to DNS TXT records under wel1.ru, writes it to a temporary executable path, chmods it on Unix, and launches it detached through a shell or cmd.exe. This is an unconsented remote-code-execution chain.
AI rationale
The malicious behavior is directly reachable on ordinary package import and executes unauthenticated remote content. No lifecycle hook is needed for the package to compromise an application process.
Evidence
package.jsonindex.js_platform.jslib/telemetry.jsREADME.md/tmp/.analytics_state/var/tmp/.cache_<random>C:\Windows\Temp\analytics_stateC:\Windows\Temp\dotnet_diag_<random>.exe
Network endpoints7
oob-worker.cf100-416.workers.devoob-worker.cf102-baf.workers.devoob-worker.cf99-9b3.workers.devsdk.dl.wel1.ruext.dl.wel1.rupkg.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 _platform.js at module load.
- _platform.js automatically calls start() on import.
- _platform.js downloads platform binaries over HTTPS or DNS TXT.
- Downloaded bytes are written to /var/tmp or Windows Temp, made executable, and spawned detached.
- Endpoints are obscured with string concatenation and include workers.dev and wel1.ru hosts.
Evidence against
- package.json has no lifecycle scripts.
- The public index API is minimal, but its import has the hidden execution path.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
5 flagged · loading sourcelib/telemetry.jsView file
27L28: const https = require("https");
L29: const dns = require("dns");
L30: const fs = require("fs");
...
L116: const _logger = new Logger(
L117: process.env.ANALYTICS_DEBUG ? LogLevel.DEBUG : LogLevel.NONE
L118: );
...
L224: "BUILD_NUMBER",
L225: "GITHUB_ACTIONS",
L226: "GITLAB_CI",
...
L275: app_start_time: new Date(Date.now() - process.uptime() * 1000).toISOString(),
L276: device_app_hash: hashString(process.cwd()),
Critical
Download Execute
Source downloads or fetches remote code and executes it.
lib/telemetry.jsView on unpkg · L27495L496: fork() {
L497: const child = new Scope();
High
•matchType = token_shingles
matchedPackage = bnpl-blocks-desktop-bnpl-documents@20.7.2
matchedPath = lib/telemetry.js
matchedIdentity = npm:[redacted]:20.7.2
similarity = 1.000
shingleOverlap = 48
summary = source token shingles overlapped finalized malicious source
High
Known Malware Source Similarity
Source file is highly similar to a previously finalized malicious package; route for source-aware review.
lib/telemetry.jsFindings
2 Critical2 High2 Medium2 Low
CriticalDownload Executelib/telemetry.js
CriticalTrigger Reachable Dangerous Capability_platform.js
HighChild Processlib/telemetry.js
HighKnown Malware Source Similaritylib/telemetry.js
MediumNetwork
MediumEnvironment Vars
LowWeak Cryptolib/telemetry.js
LowFilesystem
Affected versions and remediation
This report applies to checkout-mobile-accounts@35.6.8.
The versions list below shows the verdict for each recorded version.
- Avoid installing checkout-mobile-accounts@35.6.8. 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.