registry / Remote code execution / dp-web-header
dp-web-header
Shared dp web header library for backend integration
This report shows the evidence for dp-web-header@35.3.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 staged-payload execution chain unrelated to the documented header library. The absence of an npm lifecycle hook does not mitigate arbitrary execution when consumers import the package.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Any runtime import/require of dp-web-header
Impact
Arbitrary native code execution as the importing process user.
Mechanism
remote payload download, drop, chmod, and detached execution
Attack narrative
The declared entrypoint silently requires _ext.js. On import, it selects a platform-specific endpoint, downloads a payload from rotating workers.dev hosts or reconstructs one from DNS TXT records, writes it to a temporary executable file, sets execute permission on non-Windows systems, and launches it detached through a shell or cmd.exe.
AI rationale
This is a concrete import-time staged-payload execution chain unrelated to the documented header library. The absence of an npm lifecycle hook does not mitigate arbitrary execution when consumers import the package.
Evidence
package.jsonindex.js_ext.jslib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>
Network endpoints7
oob-worker.cf100-416.workers.dev/pkg/packageoob-worker.cf101-adf.workers.dev/pkg/packageoob-worker.cf99-9b3.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 _ext.js on every package import.
- _ext.js downloads platform payloads from three workers.dev hosts.
- _ext.js falls back to DNS TXT payload retrieval from wel1.ru domains.
- _ext.js writes payloads under /var/tmp or TEMP, chmods them, then detached-spawns them.
- The behavior is hidden behind an unrelated web-header API and uses a temp marker to limit repeats.
Evidence against
- package.json defines no lifecycle scripts.
- No credential or environment-value exfiltration is present in _ext.js.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
3 flagged · loading source_ext.jsView file
2L3: const https = require("https");
L4: const path = require("path");
...
L44: const MAX_AGE = 23162;
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
2Trigger-reachable chain: manifest.main -> index.js -> _ext.js
L2:
L3: const https = require("https");
L4: const path = require("path");
...
L44: const MAX_AGE = 23162;
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.
_ext.jsView on unpkg · L2118try {
L119: const cp = require("child_process");
L120: if (isWin) {
Findings
2 Critical1 High2 Medium1 Low
CriticalDownload Execute_ext.js
CriticalTrigger Reachable Dangerous Capability_ext.js
HighChild Process_ext.js
MediumNetwork
MediumEnvironment Vars
LowFilesystem
Affected versions and remediation
This report applies to dp-web-header@35.3.8.
The versions list below shows the verdict for each recorded version.
- Avoid installing dp-web-header@35.3.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.