testudo-pack
This report shows the evidence for testudo-pack@1.0.0, the only known version.
AI Security Review
scanned 4mo ago · by lpm-firewall-aiSource inspection confirms concealed runtime remote payload download and execution unrelated to the package's apparent packing utility. Even though postinstall is inert, the exported API contains concrete malicious remote code execution behavior.
Decision evidence
public snapshot- package.json defines postinstall: node index.js, though index.js has no top-level call.
- index.js pack() invokes _fetch() before doing package functionality.
- index.js builds obfuscated host sloth-antagonist.vercel.app and OS-specific asset paths.
- index.js downloads a binary to WinMetrics app data directory, chmods on Linux, then detached-spawns it.
- Downloaded payload names are WinService.exe on Windows and WinMetrics on Linux.
- Only package files present are package.json and index.js.
- No credential harvesting or local data exfiltration code seen in package source.
- postinstall execution alone appears inert because _fetch() is not called at top level.
Source & flagged code
3 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgA single source file combines environment access, network access, and code or shell execution; review context before blocking.
index.jsFindings
Affected versions and remediation
This report applies to testudo-pack@1.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing testudo-pack@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.