Which versions of lib-frontsga are malicious?

The following npm versions of lib-frontsga are flagged malicious: 9.999.999. Treat any of these as compromised.

How do I remediate lib-frontsga if I installed it?

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.

I already installed lib-frontsga — how do I know if it already compromised me?

If lib-frontsga 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.

Is lib-frontsga part of a known attack campaign?

Yes — lib-frontsga is associated with the IN-MAL-2026-016683 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find lib-frontsga across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for lib-frontsga (version 9.999.999). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging lib-frontsga across your stack and pipelines.

Malicious package

lib-frontsganpm

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

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for lib-frontsga (version 9.999.999). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging lib-frontsga across your stack and pipelines.
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.
Did it already run?
If lib-frontsga 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 lib-frontsga 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

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-016683

References

npmjs.com

Credits

Amazon Inspector · 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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database