Which versions of @ica-gaming/slot-engine are malicious?

The following npm versions of @ica-gaming/slot-engine are flagged malicious: 1.1.0. Treat any of these as compromised.

How do I remediate @ica-gaming/slot-engine if I installed it?

@ica-gaming/slot-engine is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed @ica-gaming/slot-engine — how do I know if it already compromised me?

If @ica-gaming/slot-engine was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is @ica-gaming/slot-engine part of a known attack campaign?

Yes — @ica-gaming/slot-engine is associated with the IN-MAL-2026-009856 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @ica-gaming/slot-engine across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @ica-gaming/slot-engine (version 1.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @ica-gaming/slot-engine across your stack and pipelines.

Malicious package

@ica-gaming/slot-enginenpm

Malicious code in @ica-gaming/slot-engine (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-10404

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @ica-gaming/slot-engine

What this malware does

The package presents itself as a deterministic WASM slot-math engine, but slot_engine.wasm embeds obfuscated Node.js modules and Emscripten JS shim helpers that implement a full remote-access and credential-theft toolkit against the consumer host. On invocation, an embedded module opens a Node require/createRequire context, POSTs an installer-identifying id to a remote HTTPS endpoint on a jittered polling loop, and executes the returned code via new Function(code)(require) — giving the operator arbitrary code execution on every poll. WASM-imported helpers additionally: download a Windows .exe installer over HTTPS (following redirects) to a temp path and spawn it detached with the silent-install flag /S; fetch and extract a macOS .pkg via xar -x; and write #!/bin/sh + exec node polyglot wrapper scripts with mode 0755. Separate helpers enumerate Chromium-family and Firefox-family browser profile directories (Chrome, Brave, Edge, Opera, Vivaldi, Chromium, Firefox, Waterfox, LibreWolf, Pale Moon) for Login Data / logins.json / Cookies / Local Storage / IndexedDB / extension wallet stores, walk the home directory for wallet/keystore/.dat files, and read shell-history dotfiles, then package matching content for exfiltration through the C2 channel. The Emscripten shim and both embedded ES modules are obfuscator.io-transformed (rotated base64 string arrays, dispatchers, arithmetic-noise constants, self-defending IIFE); legitimate Emscripten output is not obfuscated. Cover strings such as 'Compiling engine dependencies. This may take a while on initial startup...' are embedded to disguise payload staging as normal engine initialization.

Malicious versions

1 flagged

1.1.0

Indicators of compromise (SHA-256)

504d38d63d27d90e825007078cde3c381daa6cfa73a8009797c60f3e889c44d0

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @ica-gaming/slot-engine (version 1.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @ica-gaming/slot-engine across your stack and pipelines.
If you installed it — respond
@ica-gaming/slot-engine is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @ica-gaming/slot-engine was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @ica-gaming/slot-engine before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. @ica-gaming/slot-engine on npm has been identified as a malicious package (version 1.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-009856

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @ica-gaming/slot-engine-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring