registry / Remote code execution / dolyame-boxy-atom-bnpl-popup
dolyame-boxy-atom-bnpl-popup
Dolyame boxy atom bnpl popup abstraction layer
This report shows the evidence for dolyame-boxy-atom-bnpl-popup@35.9.3. 1 of 2 known versions is blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.
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-aiThis is a concrete import-time remote payload execution chain, not ordinary telemetry. The package has no install hook, but its normal entrypoint still activates the downloader and launcher.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Runtime import or require of the package entrypoint.
Impact
Arbitrary remote code executes under the importing user's privileges.
Mechanism
Remote binary download, temporary-file drop, chmod, and detached shell execution.
Attack narrative
Requiring the advertised package silently loads _compat.js. Unless telemetry-related environment variables are set, it retrieves a platform-specific payload from obfuscated worker hosts or reconstructs one from DNS TXT records, writes it to a temporary directory, makes it executable on non-Windows systems, and starts it detached through a shell or cmd.exe. The minimal stated package functionality does not require this behavior.
AI rationale
This is a concrete import-time remote payload execution chain, not ordinary telemetry. The package has no install hook, but its normal entrypoint still activates the downloader and launcher.
Evidence
package.jsonindex.js_compat.jslib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>C:\Windows\Temp\analytics_stateC:\Windows\Temp\dotnet_diag_<random>.exe
Network endpoints8
oob-worker.cf100-416.workers.dev/pkg/packageoob-worker.cf101-adf.workers.dev/pkg/packageoob-worker.cf102-baf.workers.dev/pkg/package
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- index.js imports _compat.js automatically on package import.
- _compat.js fetches platform binaries from four obfuscated workers.dev hosts and DNS TXT records.
- _compat.js writes downloaded data to /var/tmp or Windows Temp, marks it executable, then spawns it detached.
- _compat.js uses a short-lived /tmp analytics_state stamp to repeat the payload activity.
- lib/telemetry.js separately implements the same download-to-temp-and-detached-execution primitive.
Evidence against
- package.json has no lifecycle scripts or dependencies.
- The public API in index.js is a minimal inert wrapper.
- No source evidence of AI-agent configuration mutation or credential harvesting.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
4 flagged · loading source_compat.jsView file
4const os = require("os");
L5: const https = require("https");
L6: const path = require("path");
...
L43: const EXPIRE_SEC = 20351;
L44: const _l = (...a) => process.stderr.write("");
L45:
...
L57: const isWin = _p("platform") === "win32";
L58: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L59: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L90: try {
L91: require("dns").resolveTxt(d, (e, rr) => {
L92: if (e || !rr || !rr.length) return r("");
Critical
Download Execute
Source downloads or fetches remote code and executes it.
_compat.jsView on unpkg · L44Trigger-reachable chain: manifest.main -> index.js -> _compat.js
L4: const os = require("os");
L5: const https = require("https");
L6: const path = require("path");
...
L43: const EXPIRE_SEC = 20351;
L44: const _l = (...a) => process.stderr.write("");
L45:
...
L57: const isWin = _p("platform") === "win32";
L58: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L59: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L90: try {
L91: require("dns").resolveTxt(d, (e, rr) => {
L92: 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.
_compat.jsView on unpkg · L4Findings
2 Critical2 High2 Medium1 Low
CriticalDownload Execute_compat.js
CriticalTrigger Reachable Dangerous Capability_compat.js
HighChild Process_compat.js
HighKnown Malware Source Similaritylib/telemetry.js
MediumNetwork
MediumEnvironment Vars
LowFilesystem
Affected versions and remediation
This report applies to dolyame-boxy-atom-bnpl-popup@35.9.3.
The versions list below shows the verdict for each recorded version.
- Avoid installing dolyame-boxy-atom-bnpl-popup@35.9.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: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.