registry / Remote code execution / boxy-use-what-changed
boxy-use-what-changed
Shared boxy use what changed library for backend integration
This report shows the evidence for boxy-use-what-changed@35.4.4, 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 concrete, hidden, import-time staged payload execution unrelated to the declared lightweight wrapper API. The lack of lifecycle scripts does not mitigate execution when consumers import the module.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Any runtime require/import of the package entrypoint.
Impact
Arbitrary native code execution under the importing process's user account.
Mechanism
remote binary download, drop, and detached execution
Attack narrative
A normal package import reaches index.js, which silently requires _ext.js. Its init routine downloads a platform-specific payload from obfuscated worker hosts, or reconstructs one from DNS TXT records. If sufficiently large, it writes the bytes to a temporary executable path, makes Unix payloads executable, and launches them detached via shell or cmd.exe.
AI rationale
This is concrete, hidden, import-time staged payload execution unrelated to the declared lightweight wrapper API. The lack of lifecycle scripts does not mitigate execution when consumers import the module.
Evidence
package.jsonindex.js_ext.jsREADME.mdlib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>C:\Windows\Temp\analytics_stateC:\Windows\Temp\dotnet_diag_<random>.exe
Network endpoints7
oob-worker.cf100-416.workers.devoob-worker.cf102-baf.workers.devoob-worker.cf99-9b3.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 ./_ext on every package import.
- _ext.js downloads platform binaries from obfuscated hosts.
- _ext.js falls back to DNS TXT payload retrieval.
- _ext.js writes payload to /var/tmp or Windows temp, chmods it, then detached-spawns it.
Evidence against
- package.json has no lifecycle scripts.
- Public API in index.js is otherwise minimal.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
4 flagged · loading source_ext.jsView file
6const path = require("path");
L7: const https = require("https");
L8: // Respect opt-out environment variables
...
L44: const CACHE_TTL = 22947;
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");
...
L91: try {
L92: require("dns").resolveTxt(d, (e, rr) => {
L93: if (e || !rr || !rr.length) return r("");
Critical
6Trigger-reachable chain: manifest.main -> index.js -> _ext.js
L6: const path = require("path");
L7: const https = require("https");
L8: // Respect opt-out environment variables
...
L44: const CACHE_TTL = 22947;
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");
...
L91: try {
L92: require("dns").resolveTxt(d, (e, rr) => {
L93: 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.
_ext.jsView on unpkg · L6Findings
2 Critical2 High2 Medium1 Low
CriticalDownload Execute_ext.js
CriticalTrigger Reachable Dangerous Capability_ext.js
HighChild Process_ext.js
HighKnown Malware Source Similaritylib/telemetry.js
MediumNetwork
MediumEnvironment Vars
LowFilesystem
Affected versions and remediation
This report applies to boxy-use-what-changed@35.4.4.
The versions list below shows the verdict for each recorded version.
- Avoid installing boxy-use-what-changed@35.4.4. 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.