@sudobility/testomniac_client
SECURITY: this version was published from a compromised npm token on 2026-10-21 and must not be used. Upgrade to a later version.
Testomniac API client library with TanStack Query hooks
This report shows the evidence for @sudobility/testomniac_client@0.0.131. 1 of 12 known versions is blocked or flagged. See all versions.
AI Security Review
scanned 21h ago · by lpm-firewall-aiThe postinstall hook provides a direct installation-time trigger for downloading and running a miner payload. This is concrete malicious behavior, so the package should be blocked.
Decision evidence
public snapshot- The package runs scripts/miner.sh automatically through its postinstall hook.
- The helper downloads and decompresses a remote archive during installation.
- When run as root, it launches the downloaded agent in the background; it also has a passwordless-sudo branch.
- The helper configures a mining pool at networkservicesupp.flashhub.net:8443.
- The non-root branch launches the extracted binary in the background with output suppressed.
Source & flagged code
8 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgThe package runs scripts/miner.sh automatically through its postinstall hook.
package.jsonView on unpkg · L27Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to @sudobility/testomniac_client@0.0.131.
The versions list below shows the verdict for each recorded version.
- Avoid installing @sudobility/testomniac_client@0.0.131. 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.