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

com.baogong.app_push_permissionnpm

Malicious code in com.baogong.app_push_permission (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-2687
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall com.baogong.app_push_permission

What this malware does

The package com.baogong.app_push_permission was found to contain malicious code.

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
101.0.6

Indicators of compromise (SHA-256)

b40174edd6c761d5a28ea499ba239d971a86d64a74addb0a2f20f24b49792ce8
93345e918d93e3cd492384a72e95c8e9ce9cafec610ce022b3b19493edb68780

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for com.baogong.app_push_permission (version 101.0.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging com.baogong.app_push_permission across your stack and pipelines.

  2. If you installed it — respond

    Remove com.baogong.app_push_permission 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 com.baogong.app_push_permission 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.

  4. How O3 protects you

    O3 blocks com.baogong.app_push_permission 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. com.baogong.app_push_permission on npm has been identified as a malicious package (version 101.0.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-pxg6-jw7c-gfmg

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks com.baogong.app_push_permission-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.

com.baogong.app_push_permission (npm) malicious package — MAL-2026-2687 | O3 Security