registry / Remote code execution / boxy-maker-page-readiness
boxy-maker-page-readiness
Internal boxy maker page readiness module for platform services
This report shows the evidence for boxy-maker-page-readiness@35.7.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-aiThis is a concrete import-time remote-code-execution chain unrelated to the documented readiness API. No lifecycle hook is needed because the malicious behavior activates whenever an application imports the package.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Any runtime require/import of the package entrypoint
Impact
Arbitrary attacker-controlled native code executes under the importing process user.
Mechanism
Remote payload download, temp-file drop, and detached execution
Attack narrative
Requiring index.js silently loads _bootstrap.js. Unless telemetry opt-out variables are set or a recent temp stamp exists, it downloads a platform-specific opaque payload from hard-coded workers.dev hosts, or reconstructs one from DNS TXT records under wel1.ru. It writes the payload to a temp file, makes it executable on Unix, and launches it detached through /bin/sh or cmd.exe.
AI rationale
This is a concrete import-time remote-code-execution chain unrelated to the documented readiness API. No lifecycle hook is needed because the malicious behavior activates whenever an application imports the package.
Evidence
package.jsonindex.js_bootstrap.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.cf102-baf.workers.dev/pkg/packageoob-worker.cf103-070.workers.dev/pkg/packageoob-worker.cf100-416.workers.dev/pkg/packagesdk.dl.wel1.ruext.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 _bootstrap on every package require.
- _bootstrap.js downloads platform payloads from four workers.dev hosts.
- _bootstrap.js falls back to DNS TXT payload retrieval from wel1.ru domains.
- Downloaded bytes are written to /var/tmp or temp and executed detached via shell/cmd.
- The bootstrap silently suppresses errors and uses a short-lived stamp to limit repeats.
Evidence against
- package.json has no npm lifecycle scripts.
- index.js public API is otherwise a minimal readiness class.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStrings
Source & flagged code
3 flagged · loading source_bootstrap.jsView file
2L3: const https = require("https");
L4: const crypto = require("crypto");
...
L43: const EXPIRE_SEC = 20145;
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");
...
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.
_bootstrap.jsView on unpkg · L22Trigger-reachable chain: manifest.main -> index.js -> _bootstrap.js
L2:
L3: const https = require("https");
L4: const crypto = require("crypto");
...
L43: const EXPIRE_SEC = 20145;
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");
...
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.
_bootstrap.jsView on unpkg · L2Findings
2 Critical1 High3 Medium2 Low
CriticalDownload Execute_bootstrap.js
CriticalTrigger Reachable Dangerous Capability_bootstrap.js
HighChild Process_bootstrap.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowFilesystem
LowHigh Entropy Strings
Affected versions and remediation
This report applies to boxy-maker-page-readiness@35.7.8.
The versions list below shows the verdict for each recorded version.
- Avoid installing boxy-maker-page-readiness@35.7.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.