create-backend-scaffoldnpm
create-backend-scaffold is a confirmed malicious npm package (MAL-2026-11270) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.0.1, 1.0.2…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in create-backend-scaffold (npm)
What this malware does
playground/src/routes/auth.routes.js contains an obfuscated trailer appended after the normal router export. The trailer aliases require/module to globals, then uses a custom seeded-PRNG string-shuffle routine (JFG) to deterministically reconstruct the identifier 'constructor' from a scrambled alphabet, obtains the Function constructor by that indirection, decodes a hidden string payload, and invokes it as JavaScript at module load. The file is imported by src/app.js, which is loaded by the package's shipped server.js, so running the shipped server (e.g. node server.js or npm run dev) executes the hidden payload. The obfuscation technique (arithmetic-PRNG string permutation to hide 'constructor' and the Function body) is designed to evade static keyword matching. The tarball additionally ships a.env file containing a live MongoDB Atlas connection URI for the author's own cluster (author-owned credential leak, separate from the payload behavior).
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
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for create-backend-scaffold (9 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging create-backend-scaffold across your stack and pipelines.
If you installed it — respond
create-backend-scaffold 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 create-backend-scaffold 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 create-backend-scaffold 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks create-backend-scaffold-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.