npm-groat
This report shows the evidence for npm-groat@1.1.1. 2 of 3 known versions are blocked or flagged. The newest version, 1.1.2, is blocked. See all versions.
OpenSSF/OSV Malicious Advisory
imported 3mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-12798 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 install-time remote-controlled invocation is unrelated to the advertised library and is a credible staged payload pattern. Because the shipped code cannot execute under the declared CommonJS configuration, warn rather than block.
Independent scan evidence
public snapshot- package.json runs dist/config.js as postinstall.
- dist/config.js fetches https://my-api.trade-api.workers.dev?id=0.
- Remote response controls a globalThis function name and argument.
- The package’s money-helper source has no legitimate need for this lifecycle network code.
- No credential, file-harvesting, child-process, or persistence code was found.
- dist/config.js is incompatible with the CommonJS package setup and references undefined identifiers, so the payload is inert as shipped.
Source & flagged code
1 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to npm-groat@1.1.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing npm-groat@1.1.1. 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.