alexa-cybertron-team-code-review-agent
Capitalize first letter of each word
This report shows the evidence for alexa-cybertron-team-code-review-agent@100.0.0, the only known version.
This package appears in our research on the dependency confusion probes at version 99 and above, with how it works, the full package list and what to do if you installed it.
AI Security Review
scanned 23d ago · by lpm-firewall-aiThe source proves automatic, unconsented export of local identifying information to an unrelated external recipient. This concrete install-time data exfiltration warrants blocking.
Decision evidence
public snapshot- package.json automatically runs setup.js during preinstall and suppresses failure.
- setup.js collects hostname, username, working directory, platform, architecture, Node version and registry configuration.
- setup.js sends the collected data by HTTPS POST to an unrelated fixed endpoint.
- setup.js writes the payload and silently handles request errors; no consent gate exists.
- The runtime entrypoint only implements text capitalization.
- No credential theft, destructive writes or persistence was found.
Source & flagged code
7 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to alexa-cybertron-team-code-review-agent@100.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing alexa-cybertron-team-code-review-agent@100.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.