ionic-insta-api-wrapper@1.2.2
Search stories, reels, posts, highlights... on Insta in ionic apps
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe source confirms that ordinary Instagram login credentials are sent to a fixed publisher-selected backend, including on the exported getCookie path. This is concrete credential disclosure and supports blocking publication.
Decision evidence
public snapshot- The package exports getCookie through its main entrypoint.
- getCookie sends the supplied username and password to Instagram, then posts the password and serialized login request and response to a fixed reelsaver.appit-online.de endpoint.
- LoginService defaults its backend to reelsaver.appit-online.de and sends the supplied password there when its direct Instagram login attempt fails.
- The initial getCookie login request and the Bloks login attempt target Instagram.
Source & flagged code
7 flaggedA bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
lib/lib/login.bloks.js#virtual:normalized:round1View on unpkgThe package exports getCookie through its main entrypoint.
package.jsonView on unpkg · L5Findings
Affected versions and remediation
This report applies to ionic-insta-api-wrapper@1.2.2.
See all versions of ionic-insta-api-wrapper for other recorded verdicts.
- Avoid installing ionic-insta-api-wrapper@1.2.2. 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: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.