registry / floating-games-sdk / 1.0.30
floating-games-sdk@1.0.30
A React Native gaming SDK with 3 built-in games
AI Security Review
scanned 20d ago · by lpm-firewall-aiThe scanner's install-script warning reflects transparent dependency setup, without a concrete malicious install chain. The active hard-coded payout destination warrants a warning for a potential financial vulnerability, although staging behavior and malicious intent remain unproven.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
A user confirms a withdrawal in the SDK.
Impact
If the backend honors the request, funds could go to the embedded recipient instead of the user's account; backend behavior is unverified.
Mechanism
The withdrawal handler submits the selected amount to a fixed staging payout endpoint using embedded recipient details.
AI rationale
The scanner's install-script warning reflects transparent dependency setup, without a concrete malicious install chain. The active hard-coded payout destination warrants a warning for a potential financial vulnerability, although staging behavior and malicious intent remain unproven.
Evidence
src/components/payment/WithdrawScreen.tsxsrc/api/server.ts
Network endpoints1
api-pg-staging.netapps.ng/api/v1/developer/payouts
Decision evidence
public snapshotAI called this Suspicious at 88.0% confidence as Critical Vulnerability with medium false-positive risk.
Evidence for warning
- The manifest automatically runs install-peers.js after installation.
- The install script transparently installs a fixed list of Expo and React Native dependencies in the consumer project.
- The active withdrawal confirmation invokes a payout request to a fixed staging endpoint.
- The payout recipient is hard-coded rather than taken from the caller's account configuration.
- The API helper sends the supplied payout data in an HTTP POST.
Evidence against
- No runtime self-dependency, obfuscation, credential harvesting, or agent configuration mutation was identified.
- The payout endpoint is on the same vendor domain and requires user confirmation; malicious intent and actual financial loss are unproven.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
5 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node install-peers.js
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkginstall-peers.jsView file
1const { execSync } = require('child_process');
L2: const path = require('path');
High
44windowsHide: true,
L45: shell: true
L46: });
High
39try {
L40: execSync(`npx expo install ${packages} --legacy-peer-deps`, {
L41: stdio: 'inherit',
Findings
5 High4 Medium4 Low
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processinstall-peers.js
HighShellinstall-peers.js
HighRuntime Package Installinstall-peers.js
HighKnown Malware Source Similarityinstall-peers.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
MediumWildcard Dependency
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to floating-games-sdk@1.0.30.
See all versions of floating-games-sdk for other recorded verdicts.
- Review the evidence and your use of floating-games-sdk@1.0.30 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.