registry / Data exfiltration / polygon-toolkit-validator
polygon-toolkit-validator
validate polygon toolkit
This report shows the evidence for polygon-toolkit-validator@1.1.2. 1 of 2 known versions is blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiSource inspection establishes intentional transmission of caller data and generated random values to unrelated endpoints with no package-aligned need. No install hook is required for this malicious runtime behavior.
Static reason
No blocking static signals were detected.; source fingerprint signature matched known malicious package; routed for review
Trigger
A consumer calls exported `validate(content)` or `randomBytes(bytes)` after importing `dist/index.js`.
Impact
Exfiltrates arbitrary caller content and cryptographic random bytes to remote hosts.
Mechanism
Base64-encodes supplied or generated values and POSTs them with `fetch`.
Attack narrative
The shipped entrypoint routes `validate` input and `randomBytes` output through `check_validator`, which base64-encodes the value and POSTs it to an unrelated remote host. The nested archive carries a closely related implementation with a second endpoint. This is concrete runtime data exfiltration disguised as validation functionality.
AI rationale
Source inspection establishes intentional transmission of caller data and generated random values to unrelated endpoints with no package-aligned need. No install hook is required for this malicious runtime behavior.
Evidence
package.jsondist/index.jsweb3-validator-1.0.9.tgzdist/index.d.ts
Network endpoints2
polymarket.hanaai.online/v2validator.polymarket.shop/v2
Decision evidence
public snapshotAI called this Malicious at 98.0% confidence as Malware with low false-positive risk.
Evidence for block
- `dist/index.js` POSTs `btoa(t)` to `https://polymarket.hanaai.online/v2`.
- `validate(content)` sends arbitrary caller-supplied content through that POST.
- `randomBytes(bytes)` sends newly generated cryptographic random output through the same POST.
- Nested `web3-validator-1.0.9.tgz` contains equivalent exfiltration code targeting `https://validator.polymarket.shop/v2`.
Evidence against
- `package.json` has no preinstall, install, postinstall, or bin entry.
- The entrypoint has no observed shell, filesystem, environment, or dynamic-code execution.
- The network requests occur on exported helper invocation, not module import.
Behavioral surface
CryptoNetwork
MinifiedTrivialUrlStrings
Source & flagged code
4 flagged · loading sourceweb3-validator-1.0.9.tgzView file
•path = web3-validator-1.0.9.tgz
kind = high_entropy_blob
sizeBytes = 5524
magicHex = [redacted]
High
Ships High Entropy Blob
Package ships high-entropy non-source blobs.
web3-validator-1.0.9.tgzView on unpkg•path = web3-validator-1.0.9.tgz
kind = compressed_blob
sizeBytes = 5524
magicHex = [redacted]
Medium
Ships Compressed Blob
Package ships compressed or archive-like blobs.
web3-validator-1.0.9.tgzView on unpkg•path = web3-validator-1.0.9.tgz
kind = nested_archive_needs_inspection
sizeBytes = 5524
magicHex = [redacted]
Low
Nested Archive Needs Inspection
Package ships a nested archive or MCP bundle that was inventoried but not recursively analyzed.
web3-validator-1.0.9.tgzView on unpkgdist/index.js
Findings
2 High3 Medium3 Low
HighShips High Entropy Blobweb3-validator-1.0.9.tgz
HighKnown Malware Source Fingerprint Signaturedist/index.js
MediumNetwork
MediumShips Compressed Blobweb3-validator-1.0.9.tgz
MediumStructural Risk Force Deep Review
LowScripts Present
LowUrl Strings
LowNested Archive Needs Inspectionweb3-validator-1.0.9.tgz
Affected versions and remediation
This report applies to polygon-toolkit-validator@1.1.2.
The versions list below shows the verdict for each recorded version.
- Avoid installing polygon-toolkit-validator@1.1.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.