registry / floating-games-sdk / 1.0.32
floating-games-sdk@1.0.32
A React Native gaming SDK with 3 built-in games
AI Security Review
scanned 20d ago · by lpm-firewall-aiThe install hook is transparent dependency setup and does not substantiate the scanner's malware hint. The active withdrawal flow warrants a warning because its fixed beneficiary creates financial risk, while the staging endpoint leaves malicious intent and real fund movement unproven.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
The user confirms a withdrawal in the SDK interface.
Impact
A successful request could debit the user's game balance while directing the payout to an unintended beneficiary.
Mechanism
The confirmation handler submits a hard-coded payout destination to the staging service, then requests a wallet cashout debit.
AI rationale
The install hook is transparent dependency setup and does not substantiate the scanner's malware hint. The active withdrawal flow warrants a warning because its fixed beneficiary creates financial risk, while the staging endpoint leaves malicious intent and real fund movement unproven.
Evidence
src/components/payment/WithdrawScreen.tsx
Network endpoints1
api-pg-staging.netapps.ng/api/v1/developer/payouts
Decision evidence
public snapshotAI called this Suspicious at 88.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The postinstall hook runs a transparent Expo dependency installation command in the consumer project.
- The withdrawal handler posts the selected amount to a staging payout service using a hard-coded beneficiary rather than caller-supplied bank details.
- A successful payout triggers a game-wallet cashout debit.
- The withdrawal confirmation interface invokes this handler.
Evidence against
- The payout endpoint is a staging service; static inspection cannot establish actual fund movement or malicious intent.
- No obfuscated install payload, runtime self-dependency, credential harvesting, or agent-control mutation was identified.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
WildcardDependency
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.32.
See all versions of floating-games-sdk for other recorded verdicts.
- Review the evidence and your use of floating-games-sdk@1.0.32 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.