The 'xxdxa' npm package's main file (i.js) is a heavily obfuscated Immediately Invoked Function Expression (IIFE) that runs automatically when the module is loaded. In browser environments on the site noviembrenacional.com, it reads the entire page HTML, base64-encodes it, and sends it to a hardcoded canarytokens.com endpoint. It also sends status beacons to track execution progress. If the visitor is a logged-in WordPress user (excluding two specific usernames), it fetches the account edit page, extracts a CSRF nonce, and submits a forged POST request to change the user's email to an attacker-controlled address and triggers a password reset, enabling account takeover. For the 'noviembrenacional' admin user, it attempts to delete the account. In Node.js environments, the exploit throws an error caught by a handler that sends an error beacon including the installer's public IP to the attacker. The code uses string reversal, Unicode escapes, and dead-code XOR to hide URLs, DOM properties, and attacker email addresses.

This malicious package enables attackers to exfiltrate sensitive page content and perform targeted account takeover attacks on WordPress users visiting a specific domain by changing their account email and triggering password resets. For a particular admin user, it attempts account deletion. In Node.js environments, it leaks installation information to the attacker. This compromises user accounts and potentially site integrity on the targeted domain.

No official patch or remediation is currently documented. Users should immediately remove the 'xxdxa' package from their projects and avoid using it. Monitor for unauthorized account changes on affected WordPress sites, especially noviembrenacional.com. Since the package is malicious by design, do not trust any code from it. Check vendor advisories or npm security advisories for updates or removal notices. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance.