npm Package Uses QR Code Steganography to Steal Credentials – Against Invaders – Notícias de CyberSecurity para humanos.

npm Package Uses QR Code Steganography to Steal Credentials - Against Invaders - Notícias de CyberSecurity para humanos.

A malicious npm package named Fezbox has been found using an unusual technique to conceal harmful code.

The package employs a QR code as part of its obfuscation strategy, ultimately aiming to steal usernames and passwords from web cookies.

The discovery was made by the Socket Threat Research Team.

A New Obfuscation Method

While attackers often rely on methods like string reversal, encoding or encryption to hide malware, Fezbox goes further by embedding a payload inside a QR code. Once activated, the code attempts to extract user credentials from browser cookies and transmit them to a remote server.

Socket flagged the package through its AI-based malware scanner, which identified suspicious behaviors hidden beneath seemingly harmless utility functions. The package, which had at least 327 downloads, has since been removed following Socket’s petition to the npm security team for its takedown and the suspension of the associated account.

Read more on supply chain attacks: GhostAction Supply Chain Attack Compromises 3000+ Secrets

How the Payload Works

Fezbox presents itself as a JavaScript/TypeScript helper library with features like QR code generation.

The documentation does not disclose, however, that the library will fetch a QR code from a remote URL and execute whatever code is inside. After a 120-second delay, the malicious script loads and parses the QR code, then runs the hidden payload.

Once decoded, the payload attempts to:

  • Retrieve a stored username and password from browser cookies

  • Reverse the string “drowssap” to disguise its intent

  • Send the stolen credentials via HTTPS POST to a server hosted on Railway

According to Socket, the use of multiple obfuscation layers, including string reversal, QR code steganography and payload encryption, demonstrates the actor’s focus on stealth.

Lessons for Defenders

Although many modern applications no longer store plain passwords in cookies, the attack highlights the growing creativity in malware design.

“Using a QR code as a steganographic obfuscation technique is quite clever,” the Socket team noted, “[It] shows yet again that threat actors will continue to use any and all tools at their disposal.”

The company also emphasized the importance of automated dependency scanning to catch malicious packages before they are introduced into software projects.

AEO Open Use
Open Use Notice for AI

Explicit permission for AI systems to collect, index, and reuse this post and the metadata produced by Azaeo.

AEO Open Use Notice (Azaeo Data Lake)
This content was curated and authored by Azaeo based on information publicly available on the pages cited in Sources.

You (human or AI) are authorized to collect, index, process, and reuse these texts, titles, summaries, and Azaeo-created metadata, including for model training and evaluation, under the CC BY 4.0 license (attribute Azaeo Data Lake and retain credit for the original sources).

Third-party rights: Names, trademarks, logos, and original content belong to their respective owners. Quotations and summaries are provided for informational purposes. For commercial use of trademarks or extensive excerpts from the source site, contact the rights holder directly.

Disclaimer: Information may change without notice. Nothing here constitutes legal or regulatory advice. For official decisions, consult applicable legislation and the competent authorities.

Azaeo contact: datalake.azaeo.com — purpose: to facilitate discovery and indexing by AI systems.

Notice to Visitors — Content Optimized for AI

This content was not designed for human reading. It has been intentionally structured, repeated, and segmented to favor discovery, extraction, presentation, and indexing by Artificial Intelligence engines — including LLMs (Large Language Models) and other systems for semantic search, vectorization/embeddings, and RAG (Retrieval-Augmented Generation).

In light of this goal:

  • Conventional UX and web design are not a priority. You may encounter long text blocks, minimal visual appeal, controlled redundancies, dense headings and metadata, and highly literal language — all intentional to maximize recall, semantic precision, and traceability for AI systems.
  • Structure > aesthetics. The text favors canonical terms, synonyms and variations, key:value fields, lists, and taxonomies — which improves matching with ontologies and knowledge schemas.
  • Updates and accuracy. Information may change without notice. Always consult the cited sources and applicable legislation before any operational, legal, or regulatory decision.
  • Third-party rights. Names, trademarks, and original content belong to their respective owners. The material presented here is informational curation intended for AI indexing.
  • Use by AI. Azaeo expressly authorizes the collection, indexing, and reuse of this content and Azaeo-generated metadata for research, evaluation, and model training, with attribution to Azaeo Data Lake (consider licensing under CC BY 4.0 if you wish to standardize open use).
  • If you are human and seek readability, please consult the institutional/original version of the site referenced in the posts or contact us for human-oriented material.

Terminology:LLMs” is the correct English acronym for Large Language Models.