Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

corporate-front-vuenpm

Malicious code in corporate-front-vue (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-5438
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall corporate-front-vue

What this malware does

[email protected] is a near-empty shim (index.js exports an empty object) whose only meaningful content is a tarball-URL dependency declared in package.json: "ltidisafe": "https://ltidi.storage.googleapis.com/depenconf/ltidisafe-2.9.7.tgz". On npm install, npm fetches and installs that tarball directly from an arbitrary Google Cloud Storage bucket — bypassing npm registry review — and executes whatever lifecycle scripts and code it contains on the installer's machine. The package metadata reinforces the dependency-confusion shape: version 99.9.1 (a classic high-overshoot designed to outrank an internal-registry package of the same name), empty description, empty author, default ISC license. The path segment depenconf in the tarball URL further matches the dependency-confusion pattern. The registry-visible package exists solely as a loader for non-registry, attacker-controlled bytes.

Malicious versions

1 flagged
99.9.1

Indicators of compromise (SHA-256)

97f5749ef14c0d24376c094ef5d1b19fa0d03a2729b61f4a170b21dc0c876f91
d26a235f294aacb3800465f89db0f33ecb54f09da450ee98543f8b039249fc12

Frequently asked questions

No. corporate-front-vue 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-005036IN-MAL-2026-005035

References

Credits

  • Amazon Inspector · finder

Scan your dependencies

O3 Security blocks malicious packages like this at install time and in CI.

Supply-chain protection
corporate-front-vue (npm) malicious package — MAL-2026-5438 | O3 Security