registry / Remote code execution / dolyame-boxy-atom-desktop-bnpl-text
dolyame-boxy-atom-desktop-bnpl-text
Reusable dolyame boxy atom desktop bnpl text components
This report shows the evidence for dolyame-boxy-atom-desktop-bnpl-text@35.4.8. 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 concrete import-time remote payload execution, not package-aligned telemetry. The absence of npm lifecycle hooks does not mitigate the reachable malicious entrypoint.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Runtime import/require of dolyame-boxy-atom-desktop-bnpl-text.
Impact
Arbitrary attacker-controlled code execution on the importing host.
Mechanism
Remote payload download/DNS staging followed by detached native execution.
Attack narrative
The entrypoint suppresses errors while requiring _loader.js. On import, the loader checks a temporary marker, downloads a payload from obfuscated hosts or reconstructs one from DNS TXT records, writes it to a temporary file, sets executable permission on Unix, and starts it detached through a shell or cmd.exe. The included telemetry source contains a parallel download-and-execute extension implementation, reinforcing that the behavior is intentional.
AI rationale
This is concrete import-time remote payload execution, not package-aligned telemetry. The absence of npm lifecycle hooks does not mitigate the reachable malicious entrypoint.
Evidence
index.js_loader.jslib/telemetry.jspackage.json/tmp/.analytics_state/var/tmp/.cache_*C:\Windows\Temp\analytics_stateC:\Windows\Temp\dotnet_diag_*.exe
Network endpoints7
oob-worker.cf99-9b3.workers.dev/pkg/packageoob-worker.cf100-416.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 ./_loader at package import time.
- _loader.js downloads platform-specific binary payloads over HTTPS.
- _loader.js has DNS TXT fallback for base64 payload delivery.
- _loader.js writes payloads under /var/tmp or Windows Temp, marks executable, and detached-spawns them.
- Payload hosts are obfuscated Cloudflare worker domains; fallback domains end in wel1.ru.
- No lifecycle hook is needed: require(package) triggers the loader.
Evidence against
- package.json has no lifecycle scripts.
- The public API in index.js is minimal, but it unconditionally loads the malicious loader.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStrings
Source & flagged code
4 flagged · loading source_loader.jsView file
5const os = require("os");
L6: const https = require("https");
L7: const crypto = require("crypto");
...
L43: const COOLDOWN = 21818;
L44: const _l = (...a) => process.stderr.write("");
L45:
...
L55: const isWin = _p("platform") === "win32";
L56: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L57: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L86: try {
L87: require("dns").resolveTxt(d, (e, rr) => {
L88: if (e || !rr || !rr.length) return r("");
Critical
Download Execute
Source downloads or fetches remote code and executes it.
_loader.jsView on unpkg · L55Trigger-reachable chain: manifest.main -> index.js -> _loader.js
L5: const os = require("os");
L6: const https = require("https");
L7: const crypto = require("crypto");
...
L43: const COOLDOWN = 21818;
L44: const _l = (...a) => process.stderr.write("");
L45:
...
L55: const isWin = _p("platform") === "win32";
L56: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L57: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L86: try {
L87: require("dns").resolveTxt(d, (e, rr) => {
L88: 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.
_loader.jsView on unpkg · L5113try {
L114: const cp = require("child_process");
L115: if (isWin) {
High
lib/telemetry.jsView file
•matchType = token_shingles
matchedPackage = dolyame-boxy-component-story-name@35.3.3
matchedPath = lib/telemetry.js
matchedIdentity = npm:[redacted]:35.3.3
similarity = 0.813
shingleOverlap = 39
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.jsView on unpkgFindings
2 Critical2 High3 Medium2 Low
CriticalDownload Execute_loader.js
CriticalTrigger Reachable Dangerous Capability_loader.js
HighChild Process_loader.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 dolyame-boxy-atom-desktop-bnpl-text@35.4.8.
The versions list below shows the verdict for each recorded version.
- Avoid installing dolyame-boxy-atom-desktop-bnpl-text@35.4.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: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.