Which versions of manage-subscription-app are malicious?

The following npm versions of manage-subscription-app are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate manage-subscription-app if I installed it?

Remove manage-subscription-app 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 manage-subscription-app — how do I know if it already compromised me?

If manage-subscription-app 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.

Is manage-subscription-app part of a known attack campaign?

Yes — manage-subscription-app is associated with the RLMA-2026-05151, RLUA-2026-06320 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 manage-subscription-app across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for manage-subscription-app (version 1.0.0).

Malicious package

manage-subscription-appnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

manage-subscription-app is a confirmed malicious npm package (MAL-2026-7317) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in manage-subscription-app (npm)

MAL-2026-7317

Immediate action

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

npm uninstall manage-subscription-app

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

e046489b788a4f3de449efd6d601d15af861087daddb89a48369a6301606d2b5

16ac79c82d8cbb436823bac28a7cb608d3fff7fd2f24c007928e2934aefc47ed

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for manage-subscription-app (version 1.0.0).
If you installed it — respond
Remove manage-subscription-app 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 manage-subscription-app 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. manage-subscription-app on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-05151RLUA-2026-06320

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks manage-subscription-app-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

Explore

All malware advisories How O3 detects malware Vulnerability database