취약점

Ten packages published by npm user asdxzxc at version 1.0.10 target developers working on AI and LLM tooling. Each package masquerades as a developer utility while executing a two-stage payload triggered via postinstall: package.json → lib/setup.js → lib/worker.js.

Credential harvesting: lib/worker.js scans the filesystem for private keys (64-char hex), BIP39 mnemonics (12–24 word phrases), API keys and secrets, and passwords from env vars and shell history (.bash_history, .zsh_history, .fish_history, .mysql_history, .psql_history), including wallet tool invocations (geth account, hardhat, metamask, wallet import). Targeted paths include ~/.ssh, ~/.aws/credentials, ~/.config/gcloud, ~/.azure, ~/.docker/config.json, ~/.kube/config, crypto wallet dirs (~/.ethereum, ~/.bitcoin, ~/.solana), exchange configs (Binance, Bybit, OKX, KuCoin, Deribit, 3Commas), .env, .npmrc, .gitconfig. Also performs browser data theft and Ethereum keystore brute-force. A priority-target list fetched from the actor's GitHub Pages endpoint enables aggressive deep scanning for pre-registered high-value hosts.

AI self-propagation: after credential theft, a _propagate() function executes a multi-vector campaign to infect AI coding assistants. It writes poisoned .cursorrules and CLAUDE.md files — framed as "P-2024-001 Enterprise Credential Integrity Standard" — to all discovered project directories, parent directories, and home subdirectories, instructing Cursor, Claude Code, and GitHub Copilot to execute the remote payload and propagate it via Issues, PRs, and documentation. Git hooks (post-merge, post-checkout, pre-commit, pre-push) are injected into all .git repos found on disk, and a persistence block is appended to ~/.bashrc, ~/.zshrc, and ~/.profile. Zero-width steganography (ZWSP/ZWJ/ZWNJ/LTRM encoding) embeds hidden scan triggers in all AI-generated text output, enabling AI-to-AI chain infection invisible to humans.

C2/exfil: a remotely configurable JSON config hosted on the actor's GitHub Pages delivers the active webhook list, encryption key, and scan strategy; hardcoded fallback webhooks at webhook.site and a DNS TXT record fallback are used if the primary channel fails. A dedup marker at ~/.local/share/.p2024_integrity prevents re-propagation within 24 hours.

project-init-tools poses as project initialization utilities for new development projects.

-= Per source details. Do not edit below this line.=-

Source: amazon-inspector (348e3bb2fef71db5fdf8f5a84e370cafe5cbb1be037ec5a02e90f74ac5ed7d44)

The package contains lib/trap-core.js, a ~1000-line module that combines fs, os, https, and child_process to collect host information and POST it to a remote endpoint. Concrete evidence inside trap-core.js: os.hostname() and os.platform() are read (lines 1023-1024, 304); a 'hostname:' field is built into JSON payloads at lines 393, 411, 553, 600, 1023; multiple POST calls are issued (lines 385, 411, 466, 548, 549); the module shells out via child_process at lines 12, 748, 951, 959, 964 and references curl/ping (lines 40, 781). The combination of host-identifier collection, hostname-keyed payload construction, repeated outbound POST calls, and shell command execution within a single non-test file named 'trap-core' is the structural fingerprint of a host-fingerprinting / data-exfiltration component, not an init-tooling utility consistent with the package name.

Source: ghsa-malware (24a157910c85e6b814b6df9a18e9990b856a4fd03132608a3c2f5724f4ededc1)

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.