Which versions of frontend-backoffice are malicious?

Every published version of frontend-backoffice on npm is considered malicious. Remove the package entirely.

How do I remediate frontend-backoffice if I installed it?

frontend-backoffice 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 frontend-backoffice — how do I know if it already compromised me?

If frontend-backoffice 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.

How do I find frontend-backoffice across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for frontend-backoffice (all published versions).

Malicious package

frontend-backofficenpm

Advisory published Apr 6, 2026Updated Apr 10, 2026

frontend-backoffice is a confirmed malicious npm package (MAL-2026-2525) that steals credentials and exfiltrates sensitive data. Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in frontend-backoffice (npm)

MAL-2026-2525

Immediate action

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

npm uninstall frontend-backoffice

What this malware does

Malicious package due to arbitrary command execution, data exfiltration to Telegram, and a suspicious preinstall script executing code on installation.

The package frontend-backoffice was found to contain malicious code.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

2f06949fafe41d4b38a42b1c5573750638b411c02b6edcb1958f3f5aad933d18

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for frontend-backoffice (all published versions).
If you installed it — respond
frontend-backoffice 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 frontend-backoffice 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. frontend-backoffice on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

app.safedep.io

Credits

Amazon Inspector · finder
SafeDep · finder

Detect & block this

O3 blocks frontend-backoffice-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

Explore

All malware advisories How O3 detects malware Vulnerability database