camelot-ammv2-core is a malicious npm package that impersonates Camelot DEX's AMM v2 core contracts. It contains no legitimate code beyond a package.json and an install-time payload (index.js) that executes automatically during installation via preinstall and postinstall scripts. Version 1.0.0 harvests environment variables matching sensitive keywords, configuration files (~/.npmrc, ~/.gitconfig), and directory listings of key credential directories (~/.ssh, ~/.foundry/keystores, ~/.config/hardhat, ~/.config/gcloud). Version 1.1.0, published shortly after, escalates the attack by reading full contents of numerous credential files including AWS, SSH private keys, Kubernetes, Docker, netrc, PostgreSQL, Python, Git credentials, GCP credentials, local .env files, and cryptocurrency wallet keys for Solana, Anchor, NEAR, and Sui wallets. Both versions exfiltrate collected data via HTTPS POST to a webhook.site endpoint controlled by the attacker. The payload includes evasion techniques to avoid detection in sandbox or analysis environments. This package is part of a cluster of malicious packages from the same npm account targeting DeFi developers by harvesting RPC endpoints, wallet mnemonics, and API tokens.

Installation of camelot-ammv2-core versions 1.0.0, 1.1.0, or 1.1.1 results in the compromise of sensitive environment variables, credential files, and cryptocurrency wallet private keys on the installer's system. The attacker gains access to AWS credentials, SSH private keys, Kubernetes and Docker configs, API tokens, and wallet keys, enabling potential unauthorized access to cloud resources, source code repositories, blockchain wallets, and other sensitive infrastructure. The exfiltration occurs silently during package installation, with error handling to avoid detection. Any secrets present on affected systems should be considered compromised, especially wallet private keys and RPC/API tokens if version 1.1.0 or later was installed.

No official patch or remediation is available since this is a malicious package rather than a vulnerability in legitimate software. The primary mitigation is to immediately identify and uninstall any instances of camelot-ammv2-core versions 1.0.0, 1.1.0, or 1.1.1. All secrets and credentials present on affected systems at the time of installation must be rotated or revoked, prioritizing wallet private keys and RPC/API tokens. Developers should audit their dependency sources carefully to avoid typosquatting packages and use package integrity verification where possible. Monitor for any unauthorized access using compromised credentials and consider additional incident response measures as needed.