NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

qr-code-styling-tempnpm

Advisory published Updated

qr-code-styling-temp is a confirmed malicious npm package (MAL-2026-4655) that steals credentials and exfiltrates sensitive data (malicious versions 9.9.10, 9.9.11). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in qr-code-styling-temp (npm)

MAL-2026-4655
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall qr-code-styling-temp

What this malware does

The package's install lifecycle script (node index.js) and its main entry both load lib/core.js, which reads os.userInfo().username, os.hostname(), and the current working directory basename and encodes them into a subdomain of oob.sl4x0.xyz, then triggers a dns.resolve4 lookup of samsung.<user>.<host>.<cwd>.<ts>.oob.sl4x0.xyz. This is an out-of-band DNS exfiltration beacon that fires on every npm install and on every require() of the package, leaking installer identity to an attacker-controlled domain. Module names (os, dns, process, userInfo, hostname, resolve4) and the C2 domain are hidden as String.fromCharCode charcode arrays in lib/b02e30.js and lib/6ad264.js, with os and dns loaded via module.constructor._load(...) to evade static require scanners. The package name impersonates the popular qr-code-styling library but ships an unrelated API surface, and the author email [email protected] shares the same domain as the exfiltration host — confirming the typosquat lure and attacker-controlled infrastructure.

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.

Malicious versions

2 flagged
9.9.109.9.11

Indicators of compromise (SHA-256)

004a5cc51cc0e38448c56189fb4437ad113eec163f7ae1a7692b88d6aed71182
20b1cb1f8211a6eb0d5b0ec3bb8cf8819cdd1c661c806e838d62f8c157e0e37f
43b8423ecd37f8d1df1993875c76be89c795b0d55248f8cf0f03071405cca3f2
505baa75793240f5745baabd612aca9f182d02d3854e3ee0641be0eea39c6229
f3f9ff7c20d3cfe79073caf2449d6ee8241d053a0665e1f3686c0bf3f98f3b6a

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for qr-code-styling-temp (2 malicious versions).

  2. If you installed it — respond

    qr-code-styling-temp 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.

  3. Did it already run?

    If qr-code-styling-temp was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. qr-code-styling-temp on npm has been identified as a malicious package (versions 9.9.10, 9.9.11 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-003240IN-MAL-2026-003248GHSA-pp2c-4x5r-7h8jRLMA-2026-06399RLUA-2026-10778

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks qr-code-styling-temp-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

qr-code-styling-temp (npm) malicious package — MAL-2026-4655 | O3 Security