Which versions of frontend-regulations are malicious?

The following npm versions of frontend-regulations are flagged malicious: 99.9.1. Treat any of these as compromised.

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

Remove frontend-regulations from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed frontend-regulations — how do I know if it already compromised me?

If frontend-regulations 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 frontend-regulations part of a known attack campaign?

Yes — frontend-regulations is associated with the IN-MAL-2026-009855 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 frontend-regulations 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 frontend-regulations (version 99.9.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging frontend-regulations across your stack and pipelines.

Malicious package

frontend-regulationsnpm

Malicious code in frontend-regulations (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-10415

Immediate action

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

npm uninstall frontend-regulations

What this malware does

[email protected] is a near-empty wrapper (index.js exports an empty object) whose package.json declares the dependency 'ltidisafe' with the URL https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.3.3.tgz instead of a registry version. Installing this package causes npm to fetch a tarball from a Google Cloud Storage bucket unrelated to any documented publisher and place it into the installer's node_modules, where its lifecycle scripts and main entry execute during npm install. The wrapper package itself provides no functionality; its only effect is to smuggle the externally-hosted tarball into the dependency tree. The suspiciously high version number (99.9.1) combined with a hollow main entry and an off-registry dependency URL matches the dependency-chain dropper pattern.

Malicious versions

1 flagged

99.9.1

Indicators of compromise (SHA-256)

6d88817d57907505adf7d303019c78adceb6da7bedf1e3416f2b9a1e80605ca1

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for frontend-regulations (version 99.9.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging frontend-regulations across your stack and pipelines.
If you installed it — respond
Remove frontend-regulations from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If frontend-regulations 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 frontend-regulations 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. frontend-regulations on npm has been identified as a malicious package (version 99.9.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-009855

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks frontend-regulations-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring