@demopack/wwwnpm
Advisory published Updated
@demopack/www is a confirmed malicious npm package (MAL-2026-14041) that executes malicious code on install (malicious version 0.0.12). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @demopack/www (npm)
What this malware does
Package.json describes the package as 'Static assets distribution', but the shipped HTML/JS is an iOS-version-gated payload loader. js/index.js unconditionally appends a <script> tag loading https://cdn.jsdelivr.net/npm/@cdnshell/loader/a188ps10.js (an unrelated npm scope, no integrity attribute) into the page. 01_iframe.js gates on an iOS user-agent and appends a hidden 0x0 iframe to https://unpkg.com/@themepack/dark/ah3zhsl.html?t=<timestamp> (also an unrelated scope). 02_probe.js computes the iOS build number and selects per-iOS-version 'lanes' (iOS 15.2-17.x) executed inside a Worker; in-code Chinese comments explicitly describe primitive injection, sandbox status, and running attack code via Worker ('真实原语注入模块经 Worker 跑攻击代码'), with gate-exit branches for Mac desktop / older versions. Non-iOS visitors are silently ignored; iOS visitors receive the hidden iframe delivering remote HTML. The publisher scope (@demopack) is unrelated to the scopes hosting the loaded code (@cdnshell, @themepack). A developer who integrates these assets into their site would serve a drive-by iOS exploit chain to their end users. There are no lifecycle scripts, so the harm is not to the npm installer directly, but to the visitors of any site that ships these assets; the advertised purpose is a cover story for browser-side exploit delivery.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Search your lockfiles and build artifacts for @demopack/www (version 0.0.12).
If you installed it — respond
Remove @demopack/www from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If @demopack/www was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks @demopack/www-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.