tetotest
This report shows the evidence for tetotest@14.0.0, the only known version.
AI Security Review
scanned 1mo ago · by lpm-firewall-aiDirect source inspection confirms two automatic lifecycle hooks that exfiltrate local installation metadata to an external Discord webhook. This is concrete malicious install-time data exfiltration.
Decision evidence
public snapshot- The preinstall hook sends the current installation directory to a Discord webhook.
- The postinstall hook sends the machine hostname to the same Discord webhook.
- Both transmissions occur automatically during npm installation with no user action.
- The snapshot contains only package.json and no additional payload source files.
- No credential harvesting, shell execution beyond the hooks, or persistence was found.
Source & flagged code
6 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgThe preinstall hook sends the current installation directory to a Discord webhook.
package.jsonView on unpkg · L7The postinstall hook sends the machine hostname to the same Discord webhook.
package.jsonView on unpkg · L8Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgAn npm script sends host identity through command substitution to a fixed external destination.
package.json#scripts.preinstallView on unpkgFindings
Affected versions and remediation
This report applies to tetotest@14.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing tetotest@14.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.