adxaa
This report shows the evidence for adxaa@1.0.0, the only known version.
OpenSSF/OSV Malicious Advisory
imported 2mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-14058 confirms this npm version as malicious.
Advisory
MAL-2026-14058
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in adxaa (npm)
Details
The tarball stages an obfuscated JavaScript payload (i.js, with an un-obfuscated copy in original.js) that gates on window.location.href containing 'noviembrenacional.com' and then, using the victim's authenticated session (fetch with credentials:'include'), exfiltrates the current page HTML and username to a canarytokens.com submit endpoint, POSTs to /members/<user>/settings/delete-account/, and for a specific target user overwrites the account email to a hardcoded attacker ProtonMail address (nyxalor_25@proton.me) via /my-account/editar-cuenta/ before triggering /wp-login.php?action=lostpassword to seize the account through password reset. The package's declared main (a.js) is absent from the tarball and no lifecycle scripts are declared, so this code does not auto-execute on npm install or require against an arbitrary installer; the payload is staged on the registry for delivery to browsers on the targeted WordPress site.
References
Independent LPM AI assessment
SuspiciousIndependent AI assessment: suspicious. LPM AI assessed this version as suspicious; the assessments disagree.
Concrete malicious account-takeover, deletion, and exfiltration logic exists, but no lifecycle hook or declared reachable entrypoint activates it. Treat it as a staged payload carrier requiring a warning rather than a publish block.
Static reason
No blocking static signals were detected.
Trigger
Explicit loading or execution of `i.js` or `original.js` in a browser at the target domain.
Impact
Account deletion or takeover through email change and password reset; disclosure of page HTML and CSRF nonces.
Mechanism
Guarded DOM exfiltration plus authenticated account mutation.
AI rationale
Concrete malicious account-takeover, deletion, and exfiltration logic exists, but no lifecycle hook or declared reachable entrypoint activates it. Treat it as a staged payload carrier requiring a warning rather than a publish block.
Evidence
package.jsoni.jsoriginal.js
Network endpoints4
canarytokens.com/articles/tags/images/j11lq4swuzvslc96qfi9pmsji/submit.aspx/members/<username>/settings/delete-account//my-account/editar-cuenta//wp-login.php?action=lostpassword
Independent scan evidence
public snapshotAI called this Suspicious at 98.0% confidence as Malware with low false-positive risk.
Evidence for AI warning decision
- `i.js` and `original.js` contain a browser-targeted exploit invoked by `exploit()`.
- Target-domain guard checks `noviembrenacional.com` before acting.
- Posts full page HTML, usernames, and CSRF nonces to `canarytokens.com`.
- Uses authenticated same-origin requests to delete accounts or change an account email.
- Requests a password reset after changing the account email.
- `i.js` obfuscates the same destructive and exfiltration flow.
Evidence against
- `package.json` has no lifecycle scripts.
- Declared `main` is missing `a.js`, so normal package import does not reach the payload.
- No package file references `i.js` or `original.js` as an entrypoint.
Behavioral surface
Network
HighEntropyStringsMinifiedUrlStrings
NoLicense
Source & flagged code
0 flagged · loading sourceNo flagged code excerpts are attached to this scan.
Findings
6 High1 Medium3 Low
HighAi Review Evidence
HighAi Review Evidence
HighAi Review Evidence
HighAi Review Evidence
HighAi Review Evidence
HighAi Review Evidence
MediumNetwork
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to adxaa@1.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing adxaa@1.0.0. 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: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.