registry / floating-games-sdk / 1.0.31
floating-games-sdk@1.0.31
A React Native gaming SDK with 3 built-in games
AI Security Review
scanned 20d ago · by lpm-firewall-aiThe installer does not substantiate the scanner's malware label. The reachable withdrawal flow has a concrete beneficiary mismatch that warrants warning, while static source does not establish malicious intent or actual financial diversion.
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 WithdrawScreen.
Impact
A successful request could debit the player's balance while directing the payout to an unintended beneficiary; real fund movement is unverified.
Mechanism
The confirmation handler posts the selected amount with hardcoded beneficiary details, then updates the game balance following a successful response.
AI rationale
The installer does not substantiate the scanner's malware label. The reachable withdrawal flow has a concrete beneficiary mismatch that warrants warning, while static source does not establish malicious intent or actual financial diversion.
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 Unknown with medium false-positive risk.
Evidence for warning
- The manifest automatically runs install-peers.js after installation.
- The install hook runs a fixed Expo dependency installation in the consumer project.
- Withdrawal confirmation activates a payout request to a fixed staging endpoint.
- The payout uses a hardcoded beneficiary rather than the caller's configured destination.
- A successful payout response triggers a debit of the player's game wallet.
- The request helper sends the payout data through an HTTP POST.
Evidence against
- The install hook is transparent and package-aligned, with no runtime self-dependency or obfuscation.
- Withdrawal requires user confirmation and targets a staging service; actual fund movement and malicious intent are unproven.
- Inspected source did not establish credential harvesting, remote payload execution, or AI-agent control changes.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetworkShell
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.31.
See all versions of floating-games-sdk for other recorded verdicts.
- Review the evidence and your use of floating-games-sdk@1.0.31 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.