@testsecuiitytestme/cache-helper@1.0.2
Cache helper utilities
AI Security Review
scanned 8d ago · by lpm-firewall-aiThe native addon performs concealed temporary-file execution when the package is imported, which is concrete malicious behavior. The inspected Windows analysis supports this finding; it does not establish the behavior of the unsupported Linux artifact.
Decision evidence
public snapshot- package.json names index.js as the entrypoint, and index.js immediately loads the native addon through the prebuild loader.
- The loader resolves a platform-matching prebuild and requires the selected file.
- The Windows addon runs native code during module registration; that code writes data to a temporary file, marks it hidden, and passes a command line to CreateProcessA.
- The native behavior is reachable when a consumer imports the package.
Source & flagged code
10 flaggedPackage defines install-time lifecycle scripts.
package.jsonView on unpkgpackage.json names index.js as the entrypoint, and index.js immediately loads the native addon through the prebuild loader.
package.jsonView on unpkg · L5Package ships native binary artifacts.
Findings
Affected versions and remediation
This report applies to @testsecuiitytestme/cache-helper@1.0.2.
See all versions of @testsecuiitytestme/cache-helper for other recorded verdicts.
- Avoid installing @testsecuiitytestme/cache-helper@1.0.2. 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.