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

frontend-regulationsnpm

Advisory published Updated

frontend-regulations is a confirmed malicious npm package (MAL-2026-10415) that executes malicious code on install (malicious version 99.9.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in frontend-regulations (npm)

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.

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

1 flagged
99.9.1

Indicators of compromise (SHA-256)

6d88817d57907505adf7d303019c78adceb6da7bedf1e3416f2b9a1e80605ca1
19a756617f503211d34a90e7ccb5dd461201947b7b51ff25ae8a8b8a3b182c9b

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for frontend-regulations (version 99.9.1).

  2. 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.

  3. Did it already run?

    If frontend-regulations 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-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-009855GHSA-hf3r-x49q-fxm2

References

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.

Explore

frontend-regulations (npm) malicious package — MAL-2026-10415 | O3 Security