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

lib-frontsganpm

Advisory published Updated

lib-frontsga is a confirmed malicious npm package (MAL-2026-13448) that opens a backdoor for remote access (malicious version 9.999.999). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in lib-frontsga (npm)

MAL-2026-13448
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall lib-frontsga

What this malware does

Package name 'lib-frontsga' published to the public npm registry at version 9.999.999 targets an internal package name via dependency-confusion resolution. A preinstall/postinstall lifecycle script (poc.js) runs on npm install and collects host identifiers (hostname, username, cwd, Node version) together with CI/build attribution (GITHUB_REPOSITORY, GITHUB_REPOSITORY_OWNER, GITHUB_ACTOR, GITHUB_RUN_ID, GITHUB_WORKFLOW, npm_config_registry, RUNNER_NAME, AWS_REGION, and Azure/Jenkins/GitLab identifiers). The collected data is transmitted to a hardcoded Interactsh callback subdomain via DNS queries and HTTP/HTTPS POST to votspfykpbaortacnitltze3m5k5swzg6.oast.fun. Any organization that internally uses this name without a scoped/internal registry pin will resolve this public copy and execute the install-time beacon, disclosing internal build-environment fingerprints to a third-party out-of-band server.

Malicious versions

1 flagged
9.999.999

Indicators of compromise (SHA-256)

53a65c44cfdcbc89df47508f3f87fcab836f1fa2f4adf2298ecfb47cd6088038
54a99c45c191c89a8258800fe942341571e22fd307ad12907eba63f604632841

Detection & response playbook

Backdoor / remote access
  1. Find it

    Search your lockfiles and build artifacts for lib-frontsga (version 9.999.999).

  2. If you installed it — respond

    lib-frontsga establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

  3. Did it already run?

    If lib-frontsga 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. lib-frontsga on npm has been identified as a malicious package (version 9.999.999 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-016683RLMA-2026-10751

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks lib-frontsga-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Explore

lib-frontsga (npm) malicious package — MAL-2026-13448 | O3 Security