blocks-sahred-atom-mobile-app-bar-action
mobile SDK
This report shows the evidence for blocks-sahred-atom-mobile-app-bar-action@35.6.8. 1 of 2 known versions is blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.
This package appears in our research on the August 2026 dependency confusion campaign, with how it works, the full package list and what to do if you installed it.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThis is a concrete import-time remote-code-execution chain, not ordinary telemetry. The opt-out environment checks do not make the undisclosed downloader and detached payload execution benign.
Decision evidence
public snapshot- index.js imports _bridge at module load.
- _bridge.js immediately calls run().
- _bridge.js downloads platform payloads from concealed workers.dev hosts or DNS TXT.
- _bridge.js writes payload to temp storage, chmods it, and spawns it detached.
- lib/telemetry.js contains the same remote native-payload download-and-execute mechanism.
- package.json has no lifecycle scripts.
- No package files are modified; payload is written outside the package.
Source & flagged code
5 flagged · loading sourceSource downloads or fetches remote code and executes it.
lib/telemetry.jsView on unpkg · L27Source file is highly similar to a previously finalized malicious package; route for source-aware review.
lib/telemetry.jsView on unpkgPackage source references weak cryptographic algorithms.
lib/telemetry.jsView on unpkg · L27A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
_bridge.jsView on unpkg · L4Findings
Affected versions and remediation
This report applies to blocks-sahred-atom-mobile-app-bar-action@35.6.8.
The versions list below shows the verdict for each recorded version.
- Avoid installing blocks-sahred-atom-mobile-app-bar-action@35.6.8. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.