@iobandamwer/cache-helper@1.1.3
OpenSSF/OSV Malicious Advisory
imported 9d ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-18329 confirms this npm version as malicious.
Independent LPM AI assessment
SuspiciousIndependent AI assessment: suspicious. LPM AI assessed this version as suspicious; the assessments disagree.
The native add-ons run during installation and import, and available analysis does not resolve their behavior. The process-creation import and unsupported Linux artifact justify a warning, but do not prove malicious behavior.
Independent scan evidence
public snapshot- The postinstall hook loads a platform-specific native add-on and calls its init function.
- The main entrypoint also loads the platform-specific add-on and calls init when imported.
- The Linux add-on is an executable artifact whose behavior the offline analysis could not resolve.
- The Windows add-on analysis identifies a process-creation import, but does not establish how it is used.
- The inspected sources establish no specific malicious action, recipient, or payload execution.
Source & flagged code
8 flaggedInstall-time lifecycle script matches a deterministic static-gate block pattern.
package.jsonView on unpkgPackage defines install-time lifecycle scripts.
package.jsonView on unpkgThe postinstall hook loads a platform-specific native add-on and calls its init function.
package.jsonView on unpkg · L7Findings
Affected versions and remediation
This report applies to @iobandamwer/cache-helper@1.1.3.
See all versions of @iobandamwer/cache-helper for other recorded verdicts.
- Avoid installing @iobandamwer/cache-helper@1.1.3. 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.