Which versions of @demopack/www are malicious?

The following npm versions of @demopack/www are flagged malicious: 0.0.12. Treat any of these as compromised.

How do I remediate @demopack/www if I installed it?

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.

I already installed @demopack/www — how do I know if it already compromised me?

If @demopack/www was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is @demopack/www part of a known attack campaign?

Yes — @demopack/www is associated with the IN-MAL-2026-017911 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @demopack/www across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @demopack/www (version 0.0.12). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @demopack/www across your stack and pipelines.

Malicious package

@demopack/wwwnpm

@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)

MAL-2026-14041

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @demopack/www

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

1 flagged

0.0.12

Indicators of compromise (SHA-256)

d65caef119676a35e0ed5c3ef5a3be0d08c6a487c57270c802319fe68521dadd

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @demopack/www (version 0.0.12). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @demopack/www across your stack and pipelines.
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 ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @demopack/www before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. @demopack/www on npm has been identified as a malicious package (version 0.0.12 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-017911

References

npmjs.com

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database