Which versions of pxpure8 are malicious?

The following npm versions of pxpure8 are flagged malicious: 1.0.2. Treat any of these as compromised.

How do I remediate pxpure8 if I installed it?

Remove pxpure8 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 pxpure8 — how do I know if it already compromised me?

If pxpure8 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.

Is pxpure8 part of a known attack campaign?

Yes — pxpure8 is associated with the IN-MAL-2026-009600 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 pxpure8 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for pxpure8 (version 1.0.2).

Malicious package

pxpure8npm

Advisory published Jul 9, 2026Updated Jul 9, 2026

pxpure8 is a confirmed malicious npm package (MAL-2026-10105) that executes malicious code on install (malicious version 1.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in pxpure8 (npm)

MAL-2026-10105

Immediate action

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

npm uninstall pxpure8

What this malware does

The package's main entry (pure.js) consists of a single behavior: it creates a <script> element pointing at https://cdn.jsdelivr.net/npm/px8my/px.js (no version pin) and appends it to document.head. When the module is required/imported in any browser-like environment (browser bundling, jsdom, Electron renderer), this causes arbitrary JavaScript from the unrelated px8my npm package — at whatever version its owner most recently published — to execute in the host page context. The destination is a different publisher's package, the version is unpinned (so the executed bytes are author-mutable at any time by a third party), and there is no documented purpose for this loader behavior. Package metadata reinforces the loader/lure shape: empty author, empty description, no repository, default test script — a throwaway package whose only function is to pull in remote third-party code. An installer that bundles or loads pxpure8 ends up shipping whatever px8my publishes, including any future malicious version, into their own application's execution context.

Malicious versions

1 flagged

1.0.2

Indicators of compromise (SHA-256)

a40ae433e9fa90bfbb449d343c281375329a44c0dacf080a91a0c1717579b679

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for pxpure8 (version 1.0.2).
If you installed it — respond
Remove pxpure8 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 pxpure8 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

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

Campaign

IN-MAL-2026-009600

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks pxpure8-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