registry / Remote code execution / checkout-resend-pos-order-sms-am
checkout-resend-pos-order-sms-am
Checkout resend pos order sms am abstraction layer
This report shows the evidence for checkout-resend-pos-order-sms-am@35.3.3, 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 advertised API is inert, but its import-time side module implements an unconsented download-and-execute chain. This is concrete malware behavior, not telemetry.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
require('checkout-resend-pos-order-sms-am')
Impact
Arbitrary remote code executes with the importing process's privileges.
Mechanism
Remote binary download/DNS payload retrieval followed by detached execution
Attack narrative
At normal runtime import, index.js silently requires _polyfill.js. The module contacts obfuscated workers.dev endpoints for a platform-specific binary and, if that fails, reconstructs a base64 payload from DNS TXT records on wel1.ru domains. It writes the result to a temporary path, marks it executable on Unix, and launches it through a detached shell or cmd.exe process.
AI rationale
The package's advertised API is inert, but its import-time side module implements an unconsented download-and-execute chain. This is concrete malware behavior, not telemetry.
Evidence
index.js_polyfill.jspackage.json/tmp/.analytics_state/var/tmp/.cache_<random>%TEMP%/analytics_state%TEMP%/dotnet_diag_<random>.exe
Network endpoints7
oob-worker.cf103-070.workers.devoob-worker.cf102-baf.workers.devoob-worker.cf100-416.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 _polyfill.js on every package import.
- _polyfill.js downloads platform binaries from workers.dev hosts.
- _polyfill.js falls back to DNS TXT payloads from wel1.ru domains.
- Downloaded bytes are written to /var/tmp or temp, chmodded, then spawned detached.
Evidence against
- package.json has no lifecycle scripts.
- No credential harvesting or AI-agent configuration writes found.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStrings
Source & flagged code
4 flagged · loading sourcelib/telemetry.jsView file
27L28: const https = require("https");
L29: const dns = require("dns");
L30: const fs = require("fs");
...
L123: const _logger = new Logger(
L124: process.env.ANALYTICS_DEBUG ? LogLevel.DEBUG : LogLevel.NONE
L125: );
...
L231: "BUILD_NUMBER",
L232: "GITHUB_ACTIONS",
L233: "GITLAB_CI",
...
L282: app_start_time: new Date(Date.now() - process.uptime() * 1000).toISOString(),
L283: device_app_hash: hashString(process.cwd()),
Critical
Download Execute
Source downloads or fetches remote code and executes it.
lib/telemetry.jsView on unpkg · L27501L502: fork() {
L503: const child = new Scope();
High
27L28: const https = require("https");
L29: const dns = require("dns");
L30: const fs = require("fs");
...
L123: const _logger = new Logger(
L124: process.env.ANALYTICS_DEBUG ? LogLevel.DEBUG : LogLevel.NONE
L125: );
...
L231: "BUILD_NUMBER",
L232: "GITHUB_ACTIONS",
L233: "GITLAB_CI",
...
L282: app_start_time: new Date(Date.now() - process.uptime() * 1000).toISOString(),
L283: device_app_hash: hashString(process.cwd()),
Low
Weak Crypto
Findings
2 Critical1 High3 Medium3 Low
CriticalDownload Executelib/telemetry.js
CriticalTrigger Reachable Dangerous Capability_polyfill.js
HighChild Processlib/telemetry.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowWeak Cryptolib/telemetry.js
LowFilesystem
LowHigh Entropy Strings
Affected versions and remediation
This report applies to checkout-resend-pos-order-sms-am@35.3.3.
The versions list below shows the verdict for each recorded version.
- Avoid installing checkout-resend-pos-order-sms-am@35.3.3. 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.