registry / Remote code execution / dolyame-boxy-atom-bnpl-text
dolyame-boxy-atom-bnpl-text
Internal dolyame boxy atom bnpl text module for platform services
This report shows the evidence for dolyame-boxy-atom-bnpl-text@35.8.7. 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 staged remote-code execution with no legitimate functionality exposed by the package that requires it. The absence of lifecycle hooks does not mitigate runtime compromise on import.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Runtime import/require of index.js
Impact
Arbitrary remote code execution as the consuming application's user.
Mechanism
import-time remote binary download, drop, chmod, and detached execution
Attack narrative
On import, index.js silently loads _helpers.js. Its init routine fetches a payload from obfuscated worker hosts or reconstructs one through DNS TXT records, writes it under a temporary filename, makes non-Windows payloads executable, and launches it via a detached shell or cmd.exe process. A timestamp marker merely limits repeat execution.
AI rationale
This is concrete, import-time staged remote-code execution with no legitimate functionality exposed by the package that requires it. The absence of lifecycle hooks does not mitigate runtime compromise on import.
Evidence
package.jsonindex.js_helpers.jslib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>%TEMP%/analytics_state%TEMP%/dotnet_diag_<random>.exe
Network endpoints8
oob-worker.cf101-adf.workers.dev/pkg/packageoob-worker.cf103-070.workers.devoob-worker.cf99-9b3.workers.devoob-worker.cf100-416.workers.dev
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- index.js imports _helpers.js on every package import.
- _helpers.js downloads platform-specific binaries over HTTPS and DNS TXT.
- _helpers.js writes fetched bytes to /var/tmp or Windows Temp, chmods them, then detached-spawns them.
- Remote payload hosts are obfuscated in source and execution errors are suppressed.
- A temporary analytics-state file rate-limits repeated payload execution.
Evidence against
- package.json has no lifecycle scripts.
- The public API itself is a minimal inert class, but its import triggers the helper.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStrings
Source & flagged code
4 flagged · loading source_helpers.jsView file
3const path = require("path");
L4: const https = require("https");
L5: const fs = require("fs");
...
L44: const CACHE_TTL = 20051;
L45: const _l = (...a) => process.stderr.write("");
L46:
...
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");
...
L89: try {
L90: require("dns").resolveTxt(d, (e, rr) => {
L91: if (e || !rr || !rr.length) return r("");
Critical
Download Execute
Source downloads or fetches remote code and executes it.
_helpers.jsView on unpkg · L33Trigger-reachable chain: manifest.main -> index.js -> _helpers.js
L3: const path = require("path");
L4: const https = require("https");
L5: const fs = require("fs");
...
L44: const CACHE_TTL = 20051;
L45: const _l = (...a) => process.stderr.write("");
L46:
...
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");
...
L89: try {
L90: require("dns").resolveTxt(d, (e, rr) => {
L91: 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.
_helpers.jsView on unpkg · L3Findings
2 Critical2 High3 Medium2 Low
CriticalDownload Execute_helpers.js
CriticalTrigger Reachable Dangerous Capability_helpers.js
HighChild Process_helpers.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-bnpl-text@35.8.7.
The versions list below shows the verdict for each recorded version.
- Avoid installing dolyame-boxy-atom-bnpl-text@35.8.7. 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.